Clarify Requirements

Use when a delivery run's promoted (draft) requirements need the Solution Architect's own clarification pass before technical design: raising the technical/architectural questions the Business Analyst would not have surfaced — ownership gaps, integration-boundary conflicts, NFR infeasibility, contradiction with an existing decision record — and resolving every one with the human in writing. This is the clarify_requirements action of the design stretch — one Agent-tool dispatch with subagent_type solution-architect — distinct from resolve-open-questions (the BA's business-truth questions) and technical-design (which must not start while these questions are open).

BhangeeF16 Updated 0 repo stars

File contents

BhangeeF16/kaizen commit b4a6c51234

Frequently asked questions

npx get-skill add bhangeef16/clarify-requirements