菜单
Post-epic retrospective — analyze a finished epic (tickets, findings, debug logs) and distill durable lessons into the project's steering docs, so every next run is smarter and cheaper. Use after an epic closes, or when the user invokes /retro.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Database engineering standards for PostgreSQL, MySQL, MongoDB, Supabase and Firebase/Firestore — schema/index design, security, and the per-engine gotchas an agent gets wrong. Loaded on top of backend-craft when a ticket touches the database. Use when designing schema, queries, migrations or data-access.
Next.js App Router full-stack standards — server/client boundaries, the four caching layers, server-action security, route handlers, rendering/streaming, metadata, middleware limits, and Next-specific testing. Loaded on top of react-craft (and alongside backend-craft for server code) when the ticket's stack is Next.js. Use when building any Next.js route, action, or API surface.
Headless QA tooling for driving real test tools from the CLI — Postman/Newman (functional + contract), OWASP ZAP + nuclei (security/DAST, the agent-drivable substitute for Burp), and k6/JMeter/autocannon (load). Use when running a comprehensive QA/security/load sweep against a running app.
Full delivery pipeline — takes a feature/project request, plans it into Jira-like markdown tickets, builds each ticket with specialized developer agents, then runs QA, security and code-audit agents, loops a debugger agent over findings until clean, and closes with a final report. Use when the user asks to build a feature or project end-to-end, or invokes /ship.
Express.js (Node) engineering standards — layering, async error handling (Express 4 vs 5), boundary validation, security middleware, graceful shutdown, and testing. Loaded on top of backend-craft when the ticket's stack is Express. Use when building Express APIs.
NestJS engineering standards — feature-module architecture, DI discipline, DTO validation, the guard/interceptor/pipe/filter split, config, TypeORM/Prisma, and testing. Loaded on top of backend-craft when the ticket's stack is NestJS. Use when building NestJS APIs.
| name | retro |
| description | Post-epic retrospective — analyze a finished epic (tickets, findings, debug logs) and distill durable lessons into the project's steering docs, so every next run is smarter and cheaper. Use after an epic closes, or when the user invokes /retro. |
| argument-hint | [EPIC-NNN] |
$ARGUMENTS, or the most recently closed epic in
workboard/epics/. If none is closed, say so and stop.workboard/runs/EPIC-NNN.md, if present) and this contract:
Read the epic, every ticket (implementation logs, all findings sections, debug logs) and the run ledger (cycle history, escalations, drift fixes, guard stops). Extract only DURABLE lessons — things that will change how the next epic in this project runs:
- Recurring finding classes (same mistake ≥2 times) → a concrete rule worth adding to
workboard/steering/conventions.md.- Environment/tooling facts discovered the hard way (commands, quirks, flaky areas) →
workboard/steering/tech.md.- Planning misses (tickets that were too big/small, wrong dependency order, scope that had to change mid-build) → a "planning notes" line in
workboard/steering/product.md. Apply the updates directly to the steering files — keep each file under one page by pruning anything stale, and never duplicate an existing rule. Do not log one-off trivia. Return: lessons applied (bullets) + files updated.
chore(EPIC-NNN): retro.If the project has no workboard/steering/, create it from what the retro learns.