Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Enforces a structured planning workflow: exploratory spikes to test assumptions, self-contained plan directories for cold handoff to fresh agents, and markdown sprint retros to capture context across sessions. Designed for any substantial work—software features, launches, campaigns, research.
npx claudepluginhub dawid-dahl-umain/augmented-ai-development --plugin implanRun an exploratory spike, a throwaway implementation that proves whether key technical assumptions hold before the real implementation begins. Works against an existing Implan in ai-plans/ when one is present, and works standalone otherwise. Produces a spike report the HU can hand to the implementing agent or use to update the Implan. Use whenever the user says "/implan-spike", "spike this", "create a spike", "start a spike", "do a spike on X", "prove this assumption", "spike a feature", "proof of concept", or "throwaway implementation". The Spike Agent writes only inside its spike folder; it never modifies the Implan or the rest of the codebase. Do NOT activate for production implementation work, code reviews, refactors, or finishing real features; those belong to the implementing agent, not the spike agent.
Implan is an opt-in structured planning workflow. Trigger ONLY when the user explicitly invokes it ("/implan", "create an implan", "make an implan", "start an implan", "use Implan for X", "set up an Implan for Y") or is actively working inside an existing `ai-plans/` directory. Do NOT trigger for general planning conversations, even substantial ones, and do NOT trigger just because the user says things like "plan a feature", "plan a project", "plan a launch", "plan a campaign", or "set up a plan"; those phrases alone are not enough. Most planning discussions do not need Implan, and unwanted activation creates files, folders, and friction. When invoked, Implan produces a self-contained Plan Directory under `ai-plans/` containing a main plan, a mental model with diagrams, a test strategy (the Definition of Done the work iterates towards), and a notes scratchpad, designed so a fresh agent or the user themselves can pick the work up cold and execute it well. Suits anything substantial, code or otherwise (software features, product launches, campaigns, research projects, workshops, anything non-trivial). This skill is for PLANNING ONLY; execution happens in a separate session afterwards. Do NOT trigger for Claude Code's built-in Plan Mode or other planning methodologies.
Write a sprint retro to capture context for the next session. Use when user says "retro", "write a retro", "sprint retro", "fill in retro". Do NOT activate for general retrospective discussions.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI-assisted deep planning with research, interview, external LLM review, and TDD approach
AAID (Augmented AI Development) - TDD workflow enforcing disciplined RED/GREEN/REFACTOR cycles with developer-maintained architectural control
Document Driven Development — a structured workflow for AI-assisted software development with TDD, specs, and cross-review
TDD-validated implementation planning with plan review quality gate (2 skills, 5 agents, 1 command) - write plans, validate against codebase reality before execution
Helder's personal SDLC toolbelt for AI coding agents — from PRD to ship. Bundles the tracer-bullet workflow alongside TDD, code review, audits, and shipping skills.
Specification-driven development workflow: specify → plan → tasks → implement
AAID (Augmented AI Development) - TDD workflow enforcing disciplined RED/GREEN/REFACTOR cycles with developer-maintained architectural control
AAID (Augmented AI Development) - BDD/ATDD workflow using the Three-Layer Model for acceptance testing with developer-maintained architectural control
Test-quality skills for Claude Code. Currently includes AI-driven mutation testing where Claude acts as the mutation engine, identifying weak tests by mutating source code and tracking which mutants survive.
Professional TDD for AI-Augmented Software Development
🔻

📋 Repository Purpose: This repository contains support resources for developers who want to follow the
AAIDworkflow. The main methodology is introduced in our dev.to article (also available in the repo here) with detailed resources, templates, and tools provided here.
AUGMENTED AI DEVELOPMENT AAID (/eɪd/ - pronounced like "aid") is a disciplined approach where developers augment their capabilities by integrating with AI, while maintaining full architectural control. You direct the agent to generate tests and implementation code, reviewing every line and ensuring alignment with business requirements.
You're not being replaced. You're being augmented.
This separates professional software development from "vibe coding." While vibe coders blindly accept AI output and ship buggy, untested code they can't understand, AAID practitioners use TDD (Test-Driven Development) to ensure reliable agentic assistance.
Built on proven foundations from Kent Beck's TDD, Dave Farley's Continuous Delivery, Acceptance Testing and Four-Layer Model, Robert C. Martin's Three Laws of TDD, and other battle-tested practices.
AAID Acceptance Testing processAAID workflow, demonstrating the Four-Layer Model, test isolation patterns, and hexagonal architectureAAID processaaid-tdd and aaid-bdd as Claude Code plugins that enforce the workflow├── docs/
│ ├── onboarding/ # Gentle introduction to AAID
│ └── aidd-workflow.md # Complete AAID methodology guide
├── appendices/ # Supporting documentation
├── .cursor/commands/ # Cursor slash commands (copy to other tools' custom-command folders)
│ ├── planning/
│ ├── tdd/
│ ├── investigation/
│ └── misc/
├── rules/ # AI workflow rules (drop into .cursor/rules/ or CLAUDE.md)
└── plugins/ # Claude Code plugins (aaid-tdd, aaid-bdd)
docs/onboarding/guide.md: Gentle introduction to AAID with 7 progressive levels (~60 minutes total)
docs/aidd-workflow.md: The complete AAID methodology with detailed explanations, examples, and step-by-step workflows