| name | workflow |
| description | Complete development workflow from planning to GitHub PR using PARA methodology and RLM for large codebases. Use when implementing a feature, fixing a bug, refactoring, or taking work from plan to GitHub PR. |
| triggers | ["/workflow","implement a feature","fix bug end to end","refactor code","add functionality","architecture change","large codebase work","complex task","start development","plan to github"] |
Workflow Skill
Core Philosophy
"Structure + Execution = Reproducible Results."
This workflow is a pure orchestrator that coordinates specialized skills through phases. It does not implement functionality directly—it delegates to the appropriate skill for each task.
Orchestration Model:
Plan (para) → Branch → Execute (developer) → Test (testing) → Validate (reviewers) → Commit (git-commits) → PR → Monitor
Each phase invokes one or more specialized skills. The workflow ensures proper sequencing, gates, and parallel execution.
⚠️ ENFORCEMENT: Phase gates are MANDATORY. See GATES.md for all gate checklists and enforcement mechanisms.
When to Use This Workflow
Use the workflow skill when you need to:
- Implement a feature end-to-end (plan → code → test → PR)
- Fix a bug with full TDD cycle
- Refactor code with complete validation
- Take work from concept to merged PR
- Ensure quality gates are enforced (tests, code review, security)
Skip this workflow for:
- Read-only queries or explanations
- Quick fixes without tests
