By dirkkok101
Complete feature development workflow with structured SDLC phases, scope-based routing, and requirement traceability. 22 skills covering the full software development lifecycle.
Use when documents need quality convergence, user says "autoresearch", "converge", "fix all issues", or after a review reveals multiple findings.
Use after /execute, before /review, when user says "benchmark", "performance", "check speed", or before shipping performance-sensitive changes.
Use when starting any new feature, refactoring, or exploring approaches. Triggers on "brainstorm", "let's explore", "how should we approach", or when the user has a problem but no clear direction yet.
Use when learnings emerge during development — pattern discoveries, gotchas, architecture decisions, or process improvements. Triggers on "compound", "capture learning", after review cycles, after /review approval, or when insight is fresh.
Use when something is broken, tests fail unexpectedly, or behavior doesn't match expectations. Triggers on "this isn't working", "there's a bug", "why is this happening", "debug this", or "diagnose". Do NOT use for new features, performance optimization, or code quality improvements.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A complete feature development workflow for AI coding agents. Structured SDLC phases, scope-based routing, and requirement traceability from PRD through to shipped code.
Works with Claude Code, Cursor, Codex, OpenCode, and Gemini CLI.
/plugin install workflow@dirkkok-skills
git clone https://github.com/dirkkok101/skills.git ~/.codex/workflow-skills
ln -s ~/.codex/workflow-skills/skills ~/.agents/skills/workflow
gemini extensions install https://github.com/dirkkok101/skills
See .opencode/plugins/workflow.js.
/workflow:init
| Command | When to Use |
|---|---|
/workflow:init | Starting a new project, setting up docs structure |
/workflow:research | Need competitive analysis, landscape review, prior art |
/workflow:brainstorm | New feature idea, exploring approaches |
/workflow:discovery | Complex feature requiring deep domain requirements |
/workflow:prd | Writing formal product requirements |
/workflow:technical-design | Architecture, API specs, data models |
/workflow:plan | Breaking design into implementation tasks |
/workflow:beads | Creating work packages from approved plan |
/workflow:execute | Implementing from approved beads |
/workflow:review | Multi-agent code review after implementation |
/workflow:review-prd | Quality gate between PRD and design |
/workflow:review-design | Quality gate between design and plan |
/workflow:review-plan | Quality gate between plan and beads |
/workflow:review-beads | Quality gate between beads and execute |
/workflow:review-execute | Post-execution bead satisfaction verification |
/workflow:qa | Browser-based QA testing |
/workflow:benchmark | Performance benchmarking |
/workflow:security-audit | OWASP + STRIDE security audit |
/workflow:ship | Create PR with changelog and traceability |
/workflow:compound | Capture learnings for future sessions |
/workflow:diagnose | Bug investigation and root cause analysis |
/workflow:autoresearch | Automated document quality convergence |
research ─> brainstorm ─> discovery ─> prd ─> technical-design ─> plan ─> beads ─> execute
(optional) (COMP only)
execute ─> qa ─> benchmark ─> review ─> review-execute ─> security-audit ─> ship ─> compound
(opt) (opt) (opt)
Quality gates (review-*) are optional between pipeline stages.
Brainstorm classifies features and routes to the right pipeline depth:
| Scope | Pipeline |
|---|---|
| BRIEF (0-2 pts) | brainstorm → plan → beads → execute → review → ship |
| STANDARD (3-4 pts) | brainstorm → prd → technical-design → plan → beads → execute → review → ship |
| COMPREHENSIVE (5+ pts) | brainstorm → discovery → prd → technical-design → plan → beads → execute → review → ship |
| Scenario | Path |
|---|---|
| Known requirements | prd → technical-design → plan → beads → execute → review → ship |
| Technical improvement | brainstorm → technical-design → plan → beads → execute → review → ship |
| Bug fix | diagnose → fix / beads / brainstorm |
| Pre-release check | qa → benchmark → review → security-audit → ship |
Traceability Chain — Requirements trace from PRD → Design → Plan → Beads → Execute → Review. Each phase references upstream artifacts by stable FR IDs.
Intent Over Implementation — Beads carry objectives and acceptance criteria, not code. The executing agent writes code from codebase patterns.
Surgical Context — Each bead specifies exactly which files to read. Context resets between beads to prevent drift.
Self-Regulation — Execute and QA track cumulative risk scores. High scores trigger PAUSE or STOP to prevent doing more harm than good.
CONVERGE Mode — Review skills auto-fix mechanical findings and re-review until 0 FAILs or convergence. Judgment calls are escalated to the user.
Stage Gates — Every phase pauses for user approval via AskUserQuestion before proceeding. Five interaction patterns: Decision Gate, Comparison, Batch Review, Guided Review, Combined.
your-project/
├── CLAUDE.md
├── .beads/beads.db
└── docs/
├── prd/ # Requirements
├── designs/ # Technical design
├── plans/ # Implementation plans
├── execution/ # Execute manifests
├── reviews/ # Review reports
├── learnings/ # Compound learnings
├── adr/ # Architecture decisions
├── patterns/ # Coding patterns
└── architecture/ # System architecture
Required: br (beads-rust) — local issue tracking for beads
npx claudepluginhub dirkkok101/skillsDocumentation lifecycle skills: audit existing docs for gaps and staleness (docs:audit), generate and update documentation from templates (docs:write), record architectural decisions using MADR (docs:adr). Supports Diataxis framework, AI-optimization files (CLAUDE.md, AGENTS.md, llms.txt), architecture docs (C4, arc42), and project files (README, CONTRIBUTING).
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.