メニュー
Requirements + UAT design stage — acceptance criteria and Playwright test scenario authoring
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build stage — per-unit implementation with fresh context and mechanical backpressure
PK Stage — multi-AI competitive debate with iterative consensus. Sends a topic to all configured AI participants simultaneously, synthesizes the best approach, then iterates until consensus or max rounds.
Code review stage — multi-AI semantic drift detection with AC tracing
Dev Buddy web configuration portal for managing presets and pipeline config
Decomposition stage — break features into small, independently testable units of work
Discovery stage — multi-AI codebase and running app exploration
| name | dev-buddy-requirements |
| description | Requirements + UAT design stage — acceptance criteria and Playwright test scenario authoring |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, Agent, Task, TaskOutput, TaskCreate, TaskUpdate, TaskList, TaskGet |
This skill is a slash-command launcher. The authoritative workflow lives in the Dev Buddy MCP prompt dev_buddy_requirements and resource dev-buddy://prompts/dev-buddy-requirements.
dev_buddy_requirements with the caller-supplied host, current project path, and raw command arguments.get_prompt({ command: "dev-buddy-requirements", host, project_path, arguments }) and follow the returned prompt text.ralph_start, ralph_next, get_run_state, get_stage_definition, list_presets. Use those tools for deterministic work.Do not reimplement the workflow in this file; update the MCP prompt instead.