菜单
Show the current DevFlow workboard status — epics, tickets, statuses, open findings — and optionally manage tickets (add, reprioritize, block, close). Use when the user asks "what's the status", "show the board", or invokes /board.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | board |
| description | Show the current DevFlow workboard status — epics, tickets, statuses, open findings — and optionally manage tickets (add, reprioritize, block, close). Use when the user asks "what's the status", "show the board", or invokes /board. |
Read the project's workboard/ directory and give the user a Jira-style status view.
workboard/BOARD.md and every file in workboard/epics/ and workboard/tickets/
(frontmatter is enough for most; read bodies only for non-done tickets).done/total tickets).BOARD.md disagrees with ticket frontmatter, trust the tickets and fix BOARD.md./board add <description> — create a new backlog ticket (next free DEV- number,
ticket template format), update BOARD.md. Do NOT start building it./board close DEV-NNN / /board block DEV-NNN <reason> / /board priority DEV-NNN P1
— update the ticket frontmatter + board, log to the activity log./board resume — hand off to the /ship flow's resume behavior (invoke the ship skill).If workboard/ does not exist, say so and suggest running /ship "<task>" to start.
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.