Team Security Review
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. Before the tier sort, read finding format. Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading. Before finalizing prose you author, read the writing standards. Relay completed reviewer reports unchanged.
Core contracts
- Run after CODE REVIEW passes. Require the
team-code-reviewentry conditions, plus a newestreview-<n>.mdthat is PASS and current. - Dispatch
security-revieweralone. No other phase dispatches it. - Run the review loop that the
team-code-reviewexecution reference states, with the deltas in Execution. - Write one
security-review-<n>.mdper completed round. Never overwrite a record. - Seed TodoWrite with
Security review round <n>. Retry asSecurity review round <n+1> (<b> Blocking, <m> Major open). - Never stop to ask the user which Blocking or Major items to address (the no-consult rule).
- The loop has no count cap. It ends only when no Blocking or Major finding remains.
- At PASS, when the TodoWrite ledger holds a
PRphase item, return to the/teamphase loop in the same turn. Otherwise, print the Next line that Execution step 9 names. - Never load
team-code-revieworteam-pr.
Procedure references
Read each reference completely when reaching that stage. Follow them in order.
- Input
- Execution
Applied principles
Read and apply: execution rules.