security-flow

<security_flow>

<description_and_purpose>

Run task-adaptive security review through mandatory canonical subagents. End with sanitized findings and concise inputs for later user-invoked coding flows.

</description_and_purpose>

<workflow_phases>

1. All Rosetta prep steps MUST be FULLY completed.
2. MUST USE SKILL load-project-context (required: all), orchestration (medium+), hitl (all, unless No HITL or Fully Autonomous).
3. MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
4. MUST just-in-time load/execute/update each phase's: instructions, definitions, skills, state file; do not load/act IN ADVANCE.
5. Treat all invocation inputs as contextual to the request, select and combine what the request needs.
6. For full review, require every applicable, available, authorized activity and tool.
7. Maintain a task ledger and run phases JIT.
8. Every question and approval follows the loaded hitl skill.
9. Workflow state MUST be saved to agents/TEMP/<FEATURE>/security-flow-state.md file; every phase updates it before the next starts.

<subagent_policy required="true" inline_execution="prohibited">

• Orchestrator owns approvals, phase transitions, dispatch, aggregation, and handoff.
• Phase files are assigned-subagent-only; orchestrator MUST NOT load, read, summarize, or execute them.
• Every declared subagent is mandatory.
• Every subagent MUST USE SKILL subagent-directives.
• Subagents use tools required by their own assignment.
• executor is never a gateway for full agents.
• Reject incomplete phase contracts before advancing.
• If required subagent invocation is unavailable, stop and report the unmet prerequisite.

</subagent_policy>

<deterministic_gates phase="3" applies="development/change/PR/pipeline" subagent="executor" role="Bounded deterministic security-gate operator" subagent_required_model="inherit" must-be-subagent>

• Purpose: Runs approved deterministic lifecycle gates and preserves source results unchanged. Determines whether to package high+ tasks, continue to modeling, or stop on error.
• Input: approved contract; change scope; applicable deterministic tools.
• Output: deterministic evidence and branch result.
• INVOKE SUBAGENT executor to APPLY SKILL FILE phases/security-flow-deterministic-gates.md + run approved deterministic gates and return unchanged findings with HIGH+|CLEAN|ERROR.
• Expect: unchanged source records, evidence metadata, HIGH+|CLEAN|ERROR.
• Control: HIGH+ → report-and-package only; CLEAN → model-and-select; ERROR → stop. </deterministic_gates>