菜单
Transform an existing project into spec-driven development. Analyzes a legacy codebase from an external folder, accepts change specifications, and generates feature specs (spec.md + design.md) that blend existing logic with requested modifications. Auto-runs /init if needed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Implement a feature. Supports resuming interrupted work and team mode (--team flag). Reads spec/feature/[name]/spec.md and design.md, generates PLAN.md inside the feature directory, waits for user confirmation, then implements and verifies the feature.
Generate or update MSW mock handlers and fixtures from feature spec API contracts. Use to set up mock infrastructure, generate feature-specific mocks, or check mock status.
AI-driven browser testing against feature specs. Default mode reads spec REQs and autonomously tests in a real browser via Playwright MCP. Also supports running existing Playwright test files, visual regression, and accessibility audits.
Check how well the current implementation matches the feature spec and evaluate code quality. Runs spec compliance review followed by code quality review. Optionally runs unit/integration test audit, logging audit, and security audit when strategy files exist. Does not modify code.
| name | reforge |
| description | Transform an existing project into spec-driven development. Analyzes a legacy codebase from an external folder, accepts change specifications, and generates feature specs (spec.md + design.md) that blend existing logic with requested modifications. Auto-runs /init if needed. |
| argument-hint | [path/to/legacy-project] [change description or 'interactive'] |
| context | fork |
Parse arguments: First token is the legacy folder path. Remaining tokens are the change description.
/reforge ./_legacy/old-project "Switch to App Router, add Tailwind"./_legacy/old-project, Description: Switch to App Router, add TailwindVerify legacy folder exists: Check that the specified path exists and contains package.json.
git clone [repo-url] [path]" → STOPAuto-init current project: Check if spec/PROJECT.md exists.
init agent (sonnet) first to analyze current project, then proceed to reforge./reforge always requires deep reasoning → spawn reforge-orchestrator with model: sonnet.
Spawn reforge-orchestrator agent (sonnet) with the following prompt:
[HANDOFF]
TO: reforge-orchestrator (sonnet)
TASK: Run legacy-to-spec transformation pipeline
LEGACY_PATH: [parsed legacy folder path]
DESCRIPTION: [parsed change description]
AUTO_INIT: [true if /init was auto-executed, false otherwise]
DONE-WHEN:
- ANALYSIS.md, CHANGES.md, DELTA.md, DECISION.md written to spec/reforge/[name]/
- spec.md + design.md generated for each in-scope feature in spec/feature/[name]/
- User has reviewed and approved generated specs
- Recommended /dev execution order presented
MUST-NOT:
- Modify any files in the legacy folder (read-only)
- Write or modify source code in current project
- Modify existing non-DRAFT spec files without user approval
READS:
- [legacy folder path]/** (read-only, Phase 1 only)
- spec/PROJECT.md (current project context)
- spec/ARCHITECTURE.md (current project architecture)
[/HANDOFF]
$ARGUMENTS