@brunosps00/dev-workflow
v0.1.2
Published
AI-driven development workflow commands for any project. Scaffolds a complete PRD-to-PR pipeline with multi-platform AI assistant support.
Maintainers
Readme
dev-workflow
AI-driven development workflow commands for any project. Scaffolds a complete PRD-to-PR pipeline with multi-platform AI assistant support.
Install
npx @brunosps00/dev-workflow initThis will:
- Ask you to select a language (English or Portuguese)
- Create
.dw/commands/with 17 workflow commands - Create
.dw/templates/with document templates - Create
.dw/rules/(populated by/dw-analyze-project) - Generate skill wrappers for Claude Code, Codex, Copilot, and OpenCode
- Configure MCP servers (Context7 + Playwright)
Commands
Planning
/dw-brainstorm
Facilitates structured ideation before opening a PRD or implementation. Explores multiple directions — conservative, balanced, and bold — with trade-offs for each, then converges on concrete next steps. No code is written or files modified.
/dw-create-prd
Creates a Product Requirements Document by first asking at least 7 clarification questions to fully understand the feature. Generates a structured PRD with numbered functional requirements focused on what and why, saved to .dw/spec/prd-[feature-name]/prd.md.
/dw-create-techspec
Generates a Technical Specification from an existing PRD after performing web searches and asking at least 7 clarification questions. Evaluates existing libraries vs custom development, defines testing strategy, branch naming, and integration architecture. Output is saved to .dw/spec/prd-[feature-name]/techspec.md.
/dw-create-tasks
Breaks down the PRD and TechSpec into implementable tasks with a target of ~6 tasks per feature (max 2 functional requirements each). Creates individual task files with subtasks and success criteria, ensuring end-to-end coverage across backend, frontend, and functional UI. Requires approval before finalizing.
Execution
/dw-run-task
Executes a single task from the task list, implementing code that follows project patterns and includes mandatory unit tests. Performs Level 1 validation (acceptance criteria + tests + standards check) and creates a commit upon completion.
/dw-run-plan
Executes all pending tasks sequentially and automatically, with Level 1 validation after each task. After all tasks are complete, performs a final Level 2 review (PRD compliance) with an interactive corrections cycle until no gaps remain or the user accepts pending items.
/dw-bugfix
Analyzes and fixes bugs with automatic triage that distinguishes between bugs, feature requests, and excessive scope. Asks exactly 3 clarification questions before proposing a solution. Supports Direct mode (executes fix immediately) and Analysis mode (--analysis) that generates a document for the techspec/tasks pipeline.
Quality
/dw-run-qa
Validates the implementation against PRD, TechSpec, and Tasks using Playwright MCP for E2E browser automation. Tests happy paths, edge cases, negative flows, and regressions while verifying WCAG 2.2 accessibility compliance. Generates a QA report, documents bugs with screenshot evidence, and detects stub/placeholder pages.
/dw-fix-qa
Fixes bugs found during QA testing with evidence-driven retesting via Playwright MCP. Runs iterative cycles of identify → fix → retest, updating QA/bugs.md and QA/qa-report.md with status and retest evidence including screenshots and logs.
/dw-review-implementation
Compares documented requirements (PRD + TechSpec + Tasks) against actual code as a Level 2 review. Maps each requirement to endpoints and tasks with evidence, identifies gaps, partial implementations, and extra undocumented code. Does not execute fixes — waits for user instruction.
/dw-code-review
Performs a formal Level 3 code review before PR creation, verifying PRD compliance, code quality (SOLID, DRY, complexity, security), and conformance with project rules in .dw/rules/. Runs tests, verifies coverage targets, and generates a persistent report with APPROVED, APPROVED WITH CAVEATS, or REJECTED status.
/dw-refactoring-analysis
Audits the codebase for code smells and refactoring opportunities using Martin Fowler's catalog. Detects bloaters, change preventers, dispensables, couplers, conditional complexity, and DRY violations, then maps each to a concrete refactoring technique with before/after code sketches. Includes coupling/cohesion metrics, SOLID analysis, and a prioritized action plan (P0-P3).
Git & PR
/dw-commit
Analyzes pending changes, groups them by feature or logical context, and creates atomic semantic commits following the Conventional Commits format. Uses allowed types: feat, fix, docs, style, refactor, perf, test, chore, ci, build.
/dw-generate-pr
Pushes the branch to remote and creates a Pull Request on GitHub with a structured description. Collects information from the PRD and modified files, runs tests, then generates a PR body with summary, changes grouped by module, test plan, and deploy notes.
Utilities
/dw-analyze-project
Scans the repository to identify tech stack, architectural patterns, naming conventions, and anti-patterns. Generates structured documentation in .dw/rules/ with a project overview (index.md) and per-module rule files containing real code examples, which are consumed by other workflow commands.
/dw-deep-research
Conducts multi-source research with citation tracking and verification across quick, standard, deep, and ultradeep modes. Executes parallel information gathering, triangulation, and cross-reference verification through 8+ phases, producing a professional report with complete bibliography.
/dw-help
Displays the complete guide of available commands, integration flows, and when to use each one. Can be invoked without arguments for the full guide or with a specific command name (e.g., /dw-help create-prd) for a detailed section.
Workflow
/dw-brainstorm
|
/dw-create-prd --> .dw/spec/prd-{name}/prd.md
|
/dw-create-techspec --> .dw/spec/prd-{name}/techspec.md
|
/dw-create-tasks --> .dw/spec/prd-{name}/tasks.md + {N}_task.md
|
/dw-run-task (or /dw-run-plan for all)
|
/dw-run-qa --> .dw/spec/prd-{name}/QA/
|
/dw-fix-qa (if bugs found)
|
/dw-review-implementation --> PRD compliance check
|
/dw-refactoring-analysis --> .dw/spec/prd-{name}/dw-refactoring-analysis.md (optional)
|
/dw-code-review --> .dw/spec/prd-{name}/QA/dw-code-review.md
|
/dw-commit + /dw-generate-prPlatform Support
| Platform | Wrapper Location | Status |
|----------|-----------------|--------|
| Claude Code | .claude/skills/ | Full support |
| Codex CLI | .codex/skills/ | Full support |
| Copilot | .agents/skills/ | Full support |
| OpenCode | .agents/skills/ | Full support |
All wrappers point to .dw/commands/ as the single source of truth.
Project Structure (after init)
your-project/
├── .dw/
│ ├── commands/ # 16 workflow command files
│ ├── templates/ # Document templates (PRD, TechSpec, etc.)
│ ├── rules/ # Project-specific rules (run /dw-analyze-project)
│ └── spec/ # PRD directories created by commands
├── .claude/
│ ├── skills/ # Claude Code wrappers
│ └── settings.json # MCP servers (Context7, Playwright)
├── .codex/skills/ # Codex CLI wrappers
└── .agents/skills/ # Copilot/OpenCode wrappersOptions
npx @brunosps00/dev-workflow init # Interactive language selection
npx @brunosps00/dev-workflow init --lang=en # English, skip prompt
npx @brunosps00/dev-workflow init --lang=pt-br # Portuguese, skip prompt
npx @brunosps00/dev-workflow init --force # Overwrite existing files
npx @brunosps00/dev-workflow update # Update commands/templates only
npx @brunosps00/dev-workflow help # Show helpGetting Started
After running npx @brunosps00/dev-workflow init:
- Run
/dw-analyze-projectin your AI assistant to generate project rules - Run
/dw-brainstormto start planning a new feature - Run
/dw-helpto see all available commands and workflows
License
MIT
