菜单
Guided conversational interview that turns plain-language needs into a valid REASONS spec (8 sections, closed frontmatter). Trigger: creating a new spec in `sdd.schema: reasons` mode.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | aiws-sdd-spec-capture |
| description | Guided conversational interview that turns plain-language needs into a valid REASONS spec (8 sections, closed frontmatter). Trigger: creating a new spec in `sdd.schema: reasons` mode. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
Turn a non-technical user's needs into a valid REASONS spec. Ask one focused question at a time in the
user's language (CA/ES/EN); headings/keys stay English (body in the project language). Re-entrant: persist
partial answers in the change-folder so a pause is safe. Schema reference: the aiws-sdd-spec-schema skill.
slug + estimated_complexity (S/M/L) + tags. Next spec_id = max(existing)+1, 3-digit.requires_authentication, §7.2 iff handles_personal_data).Maps to:
citing ≥1 acceptance criterion; every external call declares an explicit timeout.serves_html_ui / Profile B UI): produce a static HTML mockup the user signs off on first.aiws-sdd-spec-schema checklist before writing. Never save an invalid spec.Write {{paths.specs}}/<NNN>-<slug>.md with status: draft, version: v1. Record the interview summary +
hard decisions in {{paths.changes}}/<change>/. Hand off to spec review (sign-off → user-reviewed).
Generate code or tests; invent answers when a question is open (always ask); touch files outside the spec store and change-folder.
Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.
Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.
Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.
Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.
Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.
Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.