dev

name

dev

description

Structured spec-driven development workflow for projects that use a `.dev/` workspace. Use when the user wants to document existing code as reusable reference material, list `.dev` work items, write an implementation plan into `.dev/<name>/plan.md`, implement code strictly from that plan, create a refactor plan, or run an adversarial review that updates `.dev/<name>/plan.md`. Keywords: .dev folder, dev workflow, copy existing code, plan feature, execute plan, refactor analysis, adversarial review.

Dev

This skill ports the existing dev workflow to Codex.

Use it when the project follows a .dev/-based process:

• copy: analyze an existing codebase, module, file, URL, or concept and write reusable reference docs into .dev/<name>/
• list: inspect the .dev/ workspace and summarize document status
• plan: write a detailed implementation spec into .dev/<name>/plan.md
• execute: implement code from .dev/<name>/plan.md
• refactor: analyze current code and write a refactor plan
• review: perform an adversarial review and feed critical findings back into .dev/<name>/plan.md

First Rule

Before using any workflow, check whether .dev/DEV.md exists.

• If it exists, read it first.
• Treat .dev/DEV.md as project-specific instructions that override the default workflow guidance.

Routing

Read only the command doc that matches the user request:

• For documenting existing code or patterns: commands/copy.md
• For listing status: