메뉴
Teaches how to use this AI workspace (SDD, skills, MCP), for people new to AI. Trigger: when the user asks how to use the workspace, how to start, or what SDD is.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | aiws-workspace-guide |
| description | Teaches how to use this AI workspace (SDD, skills, MCP), for people new to AI. Trigger: when the user asks how to use the workspace, how to start, or what SDD is. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","source":"aiws@0.53.0","version":"1.0"} |
For developers who code but are new to AI (agents, skills, MCP, SDD). Explains what this is, how to start, and how to get value from it.
Your repo ships an AI setup for Claude Code and GitHub Copilot, all generated from one file,
AGENTS.md (the source of truth). Don't edit the mirrors — edit AGENTS.md and regenerate.
.claude/skills/./something): an action you launch in Claude Code. In .claude/commands/.AI-WORKSPACE.md — the index of everything generated.AGENTS.md: company conventions and business logic./aiws-doc-sync.AGENTS.md rules fit the current code.ai-workspace import <path>./aiws-doc-sync so the AI has a map of the current state.For non-trivial changes; each step writes a file in docs/development/changes/<change>/:
/aiws-sdd-explore → /aiws-sdd-propose → /aiws-sdd-spec → /aiws-sdd-design → /aiws-sdd-tasks → /aiws-sdd-apply →
/aiws-sdd-verify → /aiws-sdd-archive. Go in order. Small changes can skip SDD, but run /aiws-doc-sync after.
ai-workspace sync — regenerate after editing AGENTS.md/config.ai-workspace add <language|framework|environment|mcp> <id> — add tech or environment.ai-workspace doctor — health check.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.