메뉴
Add a feature to this repository the safe way — spec, locate via maps, respect Stability, surgical implementation, verification, knowledge update. Use whenever the user asks to add, build, or implement functionality.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.
Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.
Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.
Deep-mine the source code to discover implemented features; writes ai/analysis/FEATURE_CATALOG.md.
| name | add-feature |
| description | Add a feature to this repository the safe way — spec, locate via maps, respect Stability, surgical implementation, verification, knowledge update. Use whenever the user asks to add, build, or implement functionality. |
The contract: no code before a spec, no edits to frozen code, no "done" without green tests, no merge without a review and a knowledge update.
If ai/lab/specs/SPEC_<name>.md doesn't exist, draft it from SPEC_TEMPLATE.md
(goal, scope, touch list, acceptance criteria, verification). Get the user's OK.
ai/guide/MODULE_MAP.md → which modules; note Stability of every target.ai/analysis/FEATURE_CATALOG.md → the "where new code lives" decision tree and
the 3-file rule for related features.ai/lab/WORKLOG.md → recent history: was this area just changed? is the
behavior deliberate?repo-explorer.Any file in the touch list with Stability frozen or ? ⇒ stop and ask the human.
Record their approval in the spec before proceeding.
Delegate to feature-builder with the exact touch list. Conventions per
ai/guide/CONVENTIONS.md — see also reference/checklist.md.
Delegate to test-runner: narrowest suite first, then the suites the spec names.
Red or unrun ⇒ not done.
FEATURE_MAP entry; catalog amendment; MODULE_MAP if layout changed; all [inferred].
Tell the user which tags await their [verified] flip.
Request /review-change on the diff (fresh context — not this session). Append
the work's row to ai/lab/WORKLOG.md linking spec, review, and commits, and move the
feature's ai/lab/ROADMAP.md row from Planned to Shipped (cross-link spec, WORKLOG
row, and PR by feature ID).