agentdev-architecture-advisory

Invoke the architecture advisory review after requirement expansion (Step 4) and before Decision judgment (Step 5) in req-define. The parent agent builds a five-element consultation template covering requirement candidates, conflicts, Decision candidates, existing Decision relations, and judgment questions.

Trigger it when requirements may conflict with existing REQ/Decision/Design documents, create or update Decisions, change command/skill/workflow responsibility boundaries, affect external execution agents, or span multiple commands with technically uncertain tradeoffs.

The labels are confirmed facts (backed by documents or user agreement), assumptions (unverified inferences), user-confirmation items (requiring user consent), and blockers (unresolvable open issues). The parent agent holds final classification authority over these labels.

No. The advisory subagent only reads and advises; it never edits drafts, REQ, Decision, Design, Issues, or PRs. The parent agent classifies the advice and reflects confirmed items into the draft.

If advisory conditions are met but the advisory agent is unavailable, req-define reports a blocker instead of silently skipping the review. This prevents unreviewed architectural impacts from entering finalized requirements.