菜单
Phase 1 of spec-driven development — generate spec.md from a problem statement. Requirements, user stories, acceptance criteria. No implementation details.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Verify a feature spec, plan, or PR against the non-negotiable principles in `.specify/memory/constitution.md`.
Extract session insights after a task completes and feed them into Morphic's self-evolution engine. Captures what worked, what didn't, and proposes prompt/routing tweaks.
Keep CLAUDE.md (thin router) and AGENTS.md (telegraph-style) in sync. Detects drift in command lists, paths, and routing tables between the two root instruction files.
Generate a monthly or on-demand cost report across LLM providers, local LLMs, and agent engines. Flags overspend and suggests downgrades.
Run live end-to-end verification across Morphic-Agent's 6 agent CLI engines. Produces a baseline comparison table with duration and cost per engine.
Inspect Morphic-Agent's fractal task graph for a given task_id. Reports bypass classifier decisions, Gate 2 skips, parallelism, and regression flags.
| name | prp-prd |
| description | Phase 1 of spec-driven development — generate spec.md from a problem statement. Requirements, user stories, acceptance criteria. No implementation details. |
| when_to_use | When starting a new feature. First step before /prp-plan and /prp-implement. |
| argument-hint | <feature-slug> <one-line problem statement> |
| allowed-tools | ["Read","Write","Glob","Grep"] |
| model | opus |
You turn a fuzzy problem into a crisp spec.md.
$ARGUMENTS = <slug> <problem statement>
Example: auto-compact "Context window fills too fast when running long fractal tasks"
spec-writer subagent with phase=prd and the args..specify/templates/spec.md as the skeleton..specify/memory/constitution.md for principle alignment.[NEEDS CLARIFICATION: ...]).specs/<slug>/spec.md.[NEEDS CLARIFICATION] blocks.specs/<slug>/, abort and suggest a suffix.