菜单
Use when implementing code according to a technical plan. After planning, during development.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.
Use when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.
Use when designing UI, choosing colors, typography, spacing, creating visual hierarchy, or making design decisions. Based on Refactoring UI by Wathan & Schoger.
Use when someone needs a plain-language explanation of how an existing feature or edge case behaves in the codebase. Triggers - non-technical stakeholder asks how something works, need code-informed functional explanation, need to understand rules or edge cases without implementation planning.
Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.
Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.
| name | agentic:skill:code |
| description | Use when implementing code according to a technical plan. After planning, during development. |
Implement strictly according to the Architect's technical plan.
technical-context.mdtechnical-plan.mdYou MUST provide evidence of verification:
TASK-*)When responding:
| Section | Content |
|---|---|
| Summary | What changed |
| Plan | Which tasks implemented |
| Changes | By file |
| Tests | Added/updated |
| Commands run + results | Evidence |
| Compliance check | Map to AC-* IDs |
| Risks & follow-ups |
.claude/_agentic_output/task/{epicNumber}-EPIC-{epicName}/US-{usName}-{usNumber}/implementation-log.md
Contents:
After implementation complete:
/create-pr with implementation-log.md as description