メニュー
Socratic interview to create a Business Requirements Document. First step in the SDLC pipeline.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cwijayasundara/claude_harness_eng_v1 --skill brdコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | brd |
| description | Socratic interview to create a Business Requirements Document. First step in the SDLC pipeline. |
| context | fork |
| agent | planner |
/brd
No arguments. Starts an interactive Socratic interview to gather requirements and produces a structured BRD.
This is the first gate in the SDLC pipeline. Before any code is written, the planner agent interviews the human across five dimensions to surface the full problem space. The interview is Socratic: ask clarifying questions, probe assumptions, and reflect answers back for confirmation before moving on.
Before beginning the interview, invoke superpowers:brainstorming to explore the user's intent, requirements, and design space. This surfaces hidden assumptions and alternative framings before the structured Socratic interview locks in a direction. The brainstorming output feeds into the interview — it does not replace it.
Before beginning the interview, scan the working directory for existing code. Note:
This prevents proposing solutions that conflict with what is already built.
Work through each dimension in order. Do not skip dimensions. For each dimension, ask 2-4 targeted questions, then summarize what you heard and ask the human to confirm before proceeding.
Confirm: "Here is what I understand the problem and goals to be: [summary]. Is this correct?"
Confirm: "Here is the core scope and MVP as I understand it: [summary]. Anything to add or change?"
Propose 2-3 concrete implementation approaches with trade-offs. For each option:
Ask the human to choose an approach or blend aspects. Document the chosen direction and the rationale for rejecting alternatives.
Confirm: "Here is the technical direction I am capturing: [summary]. Does this match your expectations?"
Confirm: "Here are the constraints and failure scenarios I am recording: [summary]. Anything missing?"
Confirm: "Here is the UI context I have captured: [summary]. Is this complete?"
After all five dimensions are confirmed, produce a structured BRD with these sections:
specs/brd/specs/brd/brd.mdspecs/brd/feature-{name}.mdCreate the specs/brd/ directory if it does not exist.
Display the BRD and ask: "Does this BRD accurately capture the requirements? Approve to proceed to /spec, or provide corrections."
| File | Purpose |
|---|---|
specs/brd/brd.md | Full BRD for a new project |
specs/brd/feature-{name}.md | BRD for a feature addition |
Human approval is required before proceeding to /spec.
Do not auto-advance. Wait for explicit approval or correction.