メニュー
Guidelines for managing the Product-to-Technical handoff, including Quality Gates and BRD Compilation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | skill-product-handoff |
| description | Guidelines for managing the Product-to-Technical handoff, including Quality Gates and BRD Compilation. |
| tier | 1 |
| version | 1.1 |
To ensure that NO technical work begins until the Product Artifacts are Verified, Approved, and Compiled.
You MUST verify that the Product Director (p03) has signed off.
Before requesting sign-off, verify:
skill-product-analysis).skill-product-solution-blueprint).python3 [skill_path]/scripts/verify_gate.py --file docs/product/APPROVED_BACKLOG.md
Note:
[skill_path]is the path to this skill (e.g..agent/skills/skill-product-handoff).
python3 [skill_path]/scripts/sign_off.py --file docs/product/APPROVED_BACKLOG.md
Once the gate is open, you MUST compile the scattered artifacts into a single BRD.md.
python3 [skill_path]/scripts/compile_brd.py --market-file docs/product/MARKET_STRATEGY.md --vision-file docs/product/PRODUCT_VISION.md --blueprint-file docs/product/SOLUTION_BLUEPRINT.md --output-file docs/BRD.md
MARKET_STRATEGY.md, PRODUCT_VISION.md, SOLUTION_BLUEPRINT.md.docs/BRD.md.After the BRD is compiled, you initiate the Technical Phase.
python3 [skill_path]/scripts/trigger_technical.py docs/BRD.md docs/TASK.md
TASK.md for the Architect/Developer agents.This skill is primarily used by the Orchestrator (p00) or the Handoff Workflow to accept the final output from p04.
examples/example_brd.md (Typical output structure).examples/example_approved_backlog.md (Showing valid Hash format).Use when decomposing tasks into parallel sub-tasks or spawning sub-agents. Vendor-agnostic core; load a per-vendor reference for concrete tool names, directory conventions, and invocation syntax.
Use when performing Verification-Driven Development with adversarial approach. Actively challenge assumptions and find weak spots.
Use when performing VDD adversarial review with an opt-in sarcastic, provocative delivery style — a stylistic skin over vdd-adversarial mechanics (exhaustive reporting + objective bar).
Performance critic in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing OWASP security critique in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing security vulnerability assessment (OWASP, secrets, dependencies, IaC, LLM, API, MCP/agentic) or when "thinking like a hacker" to find exploits.