菜单
Generates and refines a project spec from a free-form human request. The spec is the immutable target a planner consumes. Use when starting a new run, when an existing spec needs refinement after review, or when a human wants to draft a spec collaboratively.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ai-driven-dev/framework --skill aidd-pm-05-spec命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
Capture durable project learnings. Use when the user wants to remember, record, or formalize a decision, convention, lesson, pitfall, reusable workflow, or review finding. Not for preferences or temporary notes.
基于 SOC 职业分类
正在显示 SKILL.md
| name | aidd-pm:05:spec |
| description | Generates and refines a project spec from a free-form human request. The spec is the immutable target a planner consumes. Use when starting a new run, when an existing spec needs refinement after review, or when a human wants to draft a spec collaboratively. |
Produces a complete spec from a free-form human request. The spec is the contract between human intent and downstream agents (planner, implementer, reviewer). It is immutable once validated.
/spec <request> to draft a specaidd-dev:00:sdlc orchestrator invokes this skill at Phase 1 of a runaidd-pm:04:clarityaidd-pm:03:prd (more granular than a spec)At least one of request, prd_path, or existing_spec is required.
request: <free-form human description, optional>
prd_path: <path to an existing PRD file, optional — extracted into a spec>
existing_spec: <optional path — for refinement runs>
findings: <optional — reviewer findings to address>
working_dir: <where the spec.md will be written>
Priority when multiple are provided:
existing_spec + findings → refinement run (rewrite to address findings)prd_path → extract scope, target, constraints, non-goals, done-when from the PRD into a normalized specrequest → generate from scratch using the templatespec_path: <path to the generated spec.md>
status: draft | refined
notes: <ambiguities, assumptions made, questions for the human>
existing_spec + findings): load both, address each finding, rewrite the spec.prd_path): parse the PRD, extract target / hard constraints / non-goals / done-when into the normalized spec structure. Fields the PRD doesn't cover are marked TBD: <precise question>. Implementation details from the PRD (libraries, patterns, file layout) are dropped — they belong to the plan.request only): produce a draft spec from the request using assets/spec-template.md as the structure.assets/spec-validator.yml. When information is missing, mark it TBD: <precise question> rather than guess. The reviewer will flag it and the human can answer in the next iteration.working_dir/spec.md.This skill does not self-validate. The caller (typically aidd-dev:00:sdlc) spawns the reviewer agent with assets/spec-validator.yml as validator after this skill returns. The reviewer's findings are passed back to this skill for refinement if needed.
assets/spec-template.md — canonical structure of a specassets/spec-validator.yml — checklist used by the reviewer to validate a specaidd-pm:04:clarity (when the request needs a clarification round before drafting)TBD: <question> with a precise question.