메뉴
Surface and resolve ambiguity before the spec is written: ask targeted questions about underspecified behaviour, edge cases and decisions, and record the answers. Use between proposal and spec whenever the proposal leaves choices open.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | aiws-sdd-clarify |
| description | Surface and resolve ambiguity before the spec is written: ask targeted questions about underspecified behaviour, edge cases and decisions, and record the answers. Use between proposal and spec whenever the proposal leaves choices open. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","source":"aiws@0.53.0","version":"1.0"} |
Ask targeted questions about underspecified areas and record the decisions in the change's clarify.md, so the spec that follows is unambiguous. (Idea borrowed from Spec-Kit.)
[NEEDS CLARIFICATION] markersclarify.md[NEEDS CLARIFICATION] left for the specclarify.md.Artifacts live in
docs/development/changes/<change>/and are versioned in git. Follow the SDD lifecycle in AGENTS.md and_shared/aiws-sdd-convention.md.