workflow-architect-interviewlisted

# workflow-architect-interview Drive a depth-first architectural design interview against a single requirement. Read the requirement and the existing architecture context, then walk a one-question-at-a-time conversation with the user until the system is ship-ready. Once the user approves, partition the settled decisions into ADR identifiers and compose a dispatch prompt for the publisher agent that will materialize the artifacts. This skill **writes nothing** — no ADRs, no implement-detail doc, no per-entity files, no diagrams, no commits. The final two steps (partitioning decisions into ADR IDs, composing the publisher's dispatch prompt) are bookkeeping in conversation context only; the artifacts themselves are written by a separate publisher agent named by the orchestrator at invocation time. ## When to activate Activate this skill whenever: - A requirement file at `docs/product-requirement-document/<feature-name>/requirement.md` needs an architectural design and the design has not yet been settled with the user. - The user types `/workflow-architect-interview`, or phrases like 'design the architecture for this PRD', 'interview me on the architecture for <feature>', 'start the architect interview', 'walk me through the architecture decisions for this requirement'. - A re-entry: the user wants to extend or revise an in-flight architectural decision before approval has been given. Do NOT activate when: - The user wants to write or commit architecture artifacts (ADRs, i