by nikhilw
Set of skills and workflows to ensure humans and agents stay focused while vibe-coding.
# Add to your Claude Code skills
git clone https://github.com/nikhilw/structured-agentic-workflowA pragmatic approach to building complex software with autonomous AI agents. This methodology shifts the developer's role from Individual Contributor to Engineering Manager, focusing on deterministic outcomes, architectural integrity, and continuous improvement.
Working with LLMs for software development often devolves into "vibe-based coding"—you ask for a massive feature, the AI hallucinates a messy implementation, breaks existing dependencies, and you spend the next three hours in debugging hell.
The Structured Agentic Development Workflow treats the AI not as a magical junior developer who can read your mind, but as an incredibly fast, highly capable engineer that lacks object permanence. To get senior-level results, you must provide a rigid scaffolding of context, constraints, and deterministic planning.
Benefits:
Drawbacks:
No comments yet. Be the first to share your thoughts!
Install via the skills CLI — works with Claude Code, Cursor, Gemini CLI, GitHub Copilot, and 40+ other agents:
# Install workflow skills for your agent
npx skills add nikhilw/structured-agentic-workflow
# Install for a specific agent
npx skills add nikhilw/structured-agentic-workflow -a claude-code
# Install superpowers skills separately (test-driven-development, systematic-debugging, verification-before-completion)
npx skills add obra/superpowers -s test-driven-development -s systematic-debugging -s verification-before-completion
The npx skills CLI will discover all skills in the repo, let you pick which ones to install, and symlink them into your agent's skills directory.
Note: The superpowers skills (
test-driven-development,systematic-debugging,verification-before-completion) live in a separate repo and must be installed separately. The workflow works without them, but they are strongly recommended — the build phase expects/test-driven-development, and the workflow enforces/verification-before-completionafter every review.We keep the upstream skill names verbatim (
systematic-debugging,verification-before-completion) rather than renaming them todebug/verify. Thenpx skillsCLI has no rename flag, so keeping the upstream names means installs vianpx skillsand installs via ourinstall.shboth end up with identically-named skills.
If you prefer a single command that pulls superpowers and installs everything at once:
# Clone the repo
git clone https://github.com/nikhilw/structured-agentic-workflow.git
cd structured-agentic-workflow
# Install for all supported agents (pulls superpowers automatically)
./install.sh
# Or on Windows (PowerShell — requires Developer Mode or admin)
.\install.ps1
vendor/superpowers/, then copies the adopted skills into skills/ under their upstream names.| Agent | Skills Directory |
|-------|-----------------|
| Claude Code | ~/.claude/skills/ |
| Cursor | ~/.cursor/skills/ |
| Gemini CLI | ~/.gemini/skills/ |
| GitHub Copilot | ~/.config/github-copilot/skills/ |
Note: Cursor also reads
~/.claude/skills/natively, so installing for Claude Code alone is sufficient if you use both.
All skills use the standard SKILL.md format supported by all four agents.
./install.sh --target claude # Claude Code only
./install.sh --target gemini # Gemini CLI only
./install.sh --target cursor # Cursor only
./install.sh --target copilot # GitHub Copilot only
./install.sh --local # Skip superpowers pull (use existing vendor/)
./install.sh --remove # Remove all symlinks
./install.sh --remove --target claude # Remove for a specific agent
./install.sh --list # Show agents and install status
The installer symlinks these skills from the skills/ directory:
Core workflow skills:
| Skill | Source | Description |
|-------|--------|-------------|
| agentic-workflow | This project | Orchestrates the full development lifecycle |
| workflow-config | This project | Configure workflow preferences (TDD/BDD, caveman output style) |
| brainstorm | This project | Explore approaches, challenge the design, estimate impact, produce decision documents |
| write-plan | This project | Write phased implementation plans |
| build-phase | This project | Execute one plan phase with test + review loop |
| 3p-review | This project | Independent third-person code review |
| triage | This project | Recommend next task, minimize context thrash |
| test-driven-development | superpowers | RED-GREEN-REFACTOR discipline |
| systematic-debugging | superpowers | Systematic 4-phase root cause investigation |
| verification-before-completion | superpowers | Evidence before completion claims |
Optional vendor skills (installed but not part of the workflow):
| Skill | Source | Description |
|-------|--------|-------------|
| brainstorming | superpowers | Interactive brainstorming with visual companion and spec review loop. Not used by the workflow — available if you prefer it over /brainstorm. |
The workflow supports configurable preferences via the /workflow-config skill:
/workflow-config enable caveman full
/workflow-config use bdd
/test-driven-developmentOnly one can be active at a time. The core rule — "test first, always" — applies regardless.
The workflow integrates with the caveman brevity style. When enabled, all workflow phases adapt their prose to the requested level:
| Level | Style |
|-------|-------|
| off (default) | Normal verbose output |
| lite | Shorter prose, all technical detail preserved |
| full | Terse bullets, minimal preamble |
| ultra | Maximum compression, sentence fragments |
Technical accuracy is never sacrificed — only verbosity changes.
This workflow does not bundle or vendor caveman. Caveman compatibility is built in — each skill checks memory for the configured brevity level and adapts its output independently. If you also want caveman to govern the agent's base system prompt (outside of workflow skills), install the caveman package separately.
These are core workflow guarantees and cannot be disabled:
/verification-before-completion) — always mandatorynew/ → plans/ → done/Preferences are persisted to agent memory and apply across sessions.
If the install script doesn't work on your system, you can do it by hand. There are two steps: pulling the superpowers skills, and symlinking everything into your agent's skills directory.
Clone the superpowers repo and copy the skills you need into skills/:
# Clone superpowers into a temp directory
git clone --depth 1 https://github.com/obra/superpowers.git /tmp/superpowers
# Copy the four adopted skills into vendor/ (for reference)
mkdir -p vendor/superpowers
cp -r /tmp/superpowers/skills/brainstorming vendor/superpowers/
cp -r /tmp/superpowers/skills/test-driven-development vendor/superpowers/
cp -r /tmp/superpowers/skills/systematic-debugging vendor/superpowers/
cp -r /tmp/superpowers/skills/verification-before-completion vendor/superpowers/
cp /tmp/superpowers/LICENSE vendor/superpowers/
# Copy into skills/ under their upstream names
cp -r /tmp/superpowers/skills/brainstorming skills/brainstorming
cp -r /tmp/superpowers/skills/test-driven-development skills/test-driven-development
cp -r /tmp/superpowers/skills/systematic-debugging skills/systematic-debugging
cp -r /tmp/superpowers/skills/verification-before-completion skills/verification-before-completion
# Clean up
rm -rf /tmp/superpowers
Create symlinks from the skills/ directory to your agent's global skills directory. Replace ~/.claude/skills with the appropriate path for your agent (see the table above).
macOS / Linux:
mkdir -p ~/.claude/skills
# Symlink each skill
ln -sf "$(pwd)/skills/agentic-workflow" ~/.claude/skills/agentic-workflow
ln -sf "$(pwd)/skills/brainstorming" ~/.claude/skills/brainstorming
ln -sf "$(pwd)/skills/write-plan" ~/.c