ai-driven-dev
- 125 skills
- 0 followers
- 559 repo stars
- 6 days ago last updated
- ▌ 00 Async Dev · ai-driven-dev bundleDrive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
- ▌ 01 Brainstorm · ai-driven-dev bundleClarify a vague idea through questions. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.
- ▌ 02 Backlog · ai-driven-dev bundleOrchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.
- ▌ 05 Rule Generate · ai-driven-dev bundleCreate, update, publish or delete a coding rule across host AI tools. Use when adding, changing or removing a rule, convention or coding standard. Not for skills, agents or hooks.
- ▌ 06 Agent Generate · ai-driven-dev bundleGenerate an agent across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor an agent, subagent or specialized role. Not for other artifacts like skills, rules, commands, hooks.
- ▌ 01 Sdlc · ai-driven-dev bundleOrchestrates a request from framing to a draft pull request, autonomous or supervised, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for one step.
- ▌ 00 Init · ai-driven-dev bundleTurn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.
- ▌ 01 Commit · ai-driven-dev bundleCreate atomic conventional commits; safely retry scoped hook fixes; optionally push. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release.
- ▌ 12 Cook · ai-driven-dev bundleManages project recipes and practical guides. Use when the user wants to find a recipe, document a technique, research improvements, follow an existing guide, or check that its steps are usable.
- ▌ 07 Refactor · ai-driven-dev bundleImprove code across four axes (cleanup, performance, security, architecture) by scanning and fixing, or applying a pushed audit report. Use when the user wants to refactor, optimize, harden, or remove code. Not for read-only diagnosis or adding tests.
- ▌ 02 Implement · ai-driven-dev bundleWrite an existing plan's code, phase by phase, until every acceptance criterion holds. Use when a plan exists and needs implementing. Do NOT use to write a plan, review a diff.
- ▌ 04 Audit · ai-driven-dev bundleAudit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.
- ▌ 08 Debug · ai-driven-dev bundleReproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
- ▌ 03 Assert · ai-driven-dev bundleAssert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
- ▌ 05 Review · ai-driven-dev bundleReviews a change or a diff and says whether it is ready to ship, naming every problem with its fix. Use when the user wants a change checked before it ships. Not for fixing what the review finds, and not for auditing a whole codebase.
- ▌ 06 Test · ai-driven-dev bundleWrite and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or debugging a failure.
- ▌ 01 Plan · ai-driven-dev bundleTurn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Not for writing code or reviewing a diff.
- ▌ Test · ai-driven-dev bundleHolds the two testing disciplines this package learned by paying for them, and points at the rest. Use when writing or changing a test under tests/, touching a golden snapshot, or fixing a user-reported bug. Do NOT use for tier conventions, the vitest projects, doubles, fixtures or how to run a suite — those live in `aidd_docs/memory/testing.md`. Do NOT use for writing production code — use the context skill that owns the concept (`tools`, `translate`, `distribution`, `framework`).
- ▌ Framework · ai-driven-dev bundleOwns the installation record and everything done to a project, under src/contexts/framework/ — the manifest aggregate, and the setup/install/restore/uninstall/doctor orchestration built on top of it. This is the only context allowed to reach `translate` and `distribution`. Use when adding a use-case that touches the manifest, a setup/doctor/sync/uninstall flow, a new top-level CLI orchestration, or a launcher that runs an external binary (kanban-shaped). Do NOT use for a tool's own profile or capability classes — use `tools`. Do NOT use for the translation pipeline — use `translate`. Do NOT use for where content is fetched from — use `distribution`.
- ▌ 04 Spec · ai-driven-dev bundleGenerate or refine a spec, a feature's immutable contract, from a request, a PRD, or review findings. Use when the user wants to draft or refine a spec. Not for writing code, a full PRD, or changing a locked spec.
- ▌ 01 Usage · ai-driven-dev bundleAnswer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
- ▌ 01 Acceptance QA · ai-driven-dev bundleValidate a reviewed candidate's observable behavior against its acceptance criteria and record short named videos as reviewer evidence. Use when acceptance criteria exist and a browser-observable journey needs proof it holds. Do NOT use for diff review, unit or integration tests, or application fixes.
- ▌ Resolve Conflict · ai-driven-dev bundleResolves deterministic Git conflicts or approved choices. Use when the user wants to resolve a merge, rebase, or cherry-pick conflict. Not for deciding between competing implementations or committing changes.
- ▌ 10 Batch · ai-driven-dev bundleSplit a request into independent tasks, execute them in parallel, and summarize each agent's task, status, and result. Use when the user says "batch" or asks to execute a multi-part request in parallel.
- ▌ 05 Improve · ai-driven-dev bundleReads complete conversation evidence, measures visible cost, and recommends minimal improvements. Use when the user wants to improve a conversation, reduce wasted time or tokens, or choose files to revise. Not for delivery review or automatic edits.
- ▌ Release Video · ai-driven-dev bundlePlans and renders the release video, one scene per feature shipped since the last release, with its music and interface sounds. Use when the user wants to prepare the release announcement video, change its music, or the release video check reports missing scenes. Not for publishing the video or writing release notes.
- ▌ Test 2 · ai-driven-dev bundleHolds the two testing disciplines this package learned by paying for them, and points at the rest. Use when writing or changing a test under tests/, touching a golden snapshot, or fixing a user-reported bug. Do NOT use for tier conventions, the vitest projects, doubles, fixtures or how to run a suite — those live in `aidd_docs/memory/testing.md`. Do NOT use for writing production code — use the context skill that owns the concept (`tools`, `translate`, `distribution`, `framework`, `telemetry`).
- ▌ Tools 2 · ai-driven-dev bundleDefines or modifies what the project targets, under src/contexts/tools/ — an AI/IDE tool profile, its build contract, the content-translation capability classes it composes (agents/skills/commands/rules/hooks), and its own native-plugin adapter. Use when adding a new AI or IDE tool, changing a tool's Has* capability intersection, adding or modifying a capability class, or declaring a tool's `aidd translate` build contract. Do NOT use for the canonical-to-native translation pipeline itself — use `translate`. Do NOT use for where plugin content comes from — use `distribution`. Do NOT use for manifest or install orchestration — use `framework`.
- ▌ Framework 2 · ai-driven-dev bundleOwns the installation record and everything done to a project, under src/contexts/framework/ — the manifest aggregate, and the setup/install/restore/uninstall/doctor orchestration built on top of it. This is the only context allowed to reach `translate` and `distribution`; `tools` is reachable from `telemetry` too. Use when adding a use-case that touches the manifest, a setup/doctor/sync/uninstall flow, a new top-level CLI orchestration, or a launcher that runs an external binary (kanban-shaped). Do NOT use for a tool's own profile or capability classes — use `tools`. Do NOT use for the translation pipeline — use `translate`. Do NOT use for where content is fetched from — use `distribution`.
- ▌ Telemetry 2 · ai-driven-devOwns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps records per machine. Use when adding a reader for another tool's transcript format, changing how a figure is attributed or reported, touching the sink or the identity store, or wiring a telemetry port. Do NOT use for what a tool declares about being measured — that is `kernel/measurement.ts`, read via the `tools` skill. Do NOT use for installing or removing the hook that writes the run journal into a project — that record belongs to `framework`.
- ▌ Translate 2 · ai-driven-devBuilds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing `PluginContentTranslator`, adding a build strategy, or wiring a new tool into the build registry. Do NOT use for a tool's own profile, capability classes, or build contract — use `tools`. Do NOT use for where content is fetched from — use `distribution`. Do NOT use for manifest/install orchestration — use `framework`.
- ▌ 03 Prd 2 · ai-driven-dev bundleGenerate a structured Product Requirements Document from a need, idea, or brainstorm, confirmed before save. Use when the user wants to draft or generate a PRD or product requirements. Not for user stories or a technical plan.
- ▌ 04 Spec 2 · ai-driven-dev bundleGenerate or refine a spec, a feature's immutable contract, from a request, a PRD, or review findings. Use when the user wants to draft or refine a spec. Not for writing code, a full PRD, or changing a locked spec.
- ▌ 07 Epic 2 · ai-driven-dev bundleProduces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
- ▌ 10 Task 2 · ai-driven-dev bundleProduces or refines a backlog Task for bounded delivery work without independent user value. Use when the user wants to create, link, order, estimate, transition, or complete one. Not for User Stories, Spikes, Defects, or implementation.
- ▌ Distribution 2 · ai-driven-devOwns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use `tools` or `translate`. Do NOT use for recording what got installed on a project — use `framework`.
- ▌ 01 Plan 2 · ai-driven-dev bundleTurn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Do NOT use to write code or review a diff.
- ▌ 06 Test 2 · ai-driven-dev bundleWrite and iterate tests until they pass, or validate a user journey end to end in the browser. Use when the user wants to add coverage, find what's untested, or walk a flow. Not for auditing test health or debugging a failure.
- ▌ 10 Todo 2 · ai-driven-dev bundleSplit the user prompt into independent todos and run one executor agent per todo in parallel, then report a minimal table. Use when the user says "todo" or asks to fan out a multi-part request into parallel implementations.
- ▌ 05 Spike 2 · ai-driven-dev bundleProduces an evidence-bounded spike for an uncertainty blocking estimation, feasibility, or design. Use when the user wants to frame, investigate, resume, or conclude one. Not for general research or implementation.
- ▌ 01 Hello 2 · ai-driven-dev bundleSmoke-test that confirms the aidd-ui plugin loads. Use when the user wants to verify the alpha aidd-ui plugin is installed and reachable. Not for real UI or UX design work.
- ▌ 04 Audit 2 · ai-driven-dev bundleAudit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.
- ▌ 08 Debug 2 · ai-driven-dev bundleReproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
- ▌ 09 Defect 2 · ai-driven-dev bundleProduces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.
- ▌ 03 Assert 2 · ai-driven-dev bundleAssert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
- ▌ 05 Review 2 · ai-driven-dev bundleReview a diff read-only on three axes, code, behavior versus the plan, and relevancy, into one verdict report. Use before shipping a change. Not for fixing findings or auditing a codebase.
- ▌ 01 Commit 2 · ai-driven-dev bundleCreate an atomic git commit with a conventional message, optionally pushing. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release.
- ▌ 12 Cook 2 · ai-driven-dev bundleManage project recipes/how-to sheets by listing, creating, updating, researching, or applying a recipe. Use for recipe, cook, /cook, list, new, update, research, apply.
- ▌ 07 Refactor 2 · ai-driven-dev bundleImprove code across four axes (cleanup, performance, security, architecture) by scanning and fixing, or applying a pushed audit report. Use when the user wants to refactor, optimize, harden, or remove code. Not for read-only diagnosis or adding tests.
- ▌ 09 For Sure 2 · ai-driven-dev bundleRun an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals.
- ▌ 10 Learn 2 · ai-driven-dev bundleCapture durable project learnings. Use when the user wants to remember, record, or formalize a decision, convention, lesson, pitfall, reusable workflow, or review finding. Not for preferences or temporary notes.
- ▌ 02 Implement 2 · ai-driven-dev bundleWrite an existing plan's code, phase by phase, until every acceptance criterion holds. Use when a plan exists and needs implementing. Do NOT use to write a plan, review a diff.
- ▌ 00 Repo Init 2 · ai-driven-dev bundleInitialize a project repository with git init, a default branch, a bootstrap commit, CONTRIBUTING.md, and optionally the remote. Use when the user wants to init or set up a new repo, or publish to a remote. Not for committing, opening a PR, or tagging.
- ▌ 11 Browser QA 2 · ai-driven-dev bundleRun post-review browser QA and produce short named videos for a locked happy path and sourced browser edge cases. Use when the user wants concise reviewer evidence for a web journey. Not for API, CLI, automated tests, diff review, or application fixes.
- ▌ 01 Ticket Info 2 · ai-driven-dev bundleRetrieve and display a ticket from the configured ticketing tool. Use when the user wants to see, show, or look up a ticket's details. Not for creating a ticket, or commenting on, transitioning, or reassigning one.
- ▌ 00 Init 2 · ai-driven-dev bundleTurns AIDD measurement on for a project, proves it is recording, lets a person opt into (or out of) naming themselves on their own records, and removes what was measured when asked. Use when the user wants to start measuring what their work costs, wants to stop, asks why nothing is being recorded, wants their own name to appear on (or disappear from) what gets measured, or wants their measured data deleted. Not for answering what a piece of work consumed.
- ▌ 01 Cost 2 · ai-driven-dev bundleAnswers what a period or one task consumed - a total, a day-by-day series, or a breakdown by step, model, task, backlog item, orchestrated flow, tool, project or person - and hands back the artefact each question deserves. Use when the user asks what a piece of work cost, what changed, where the effort went, which task, which backlog item or ticket, which orchestrated run, for which project, or who spent it. Not for turning measurement on.
- ▌ 00 Onboard 2 · ai-driven-dev bundleGuide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
- ▌ 09 Mermaid 2 · ai-driven-dev bundleGenerate a valid Mermaid diagram from a written source through a plan, generate, review loop. Use when the user wants to turn an architecture, lifecycle, or flow into a Mermaid diagram. Not for other diagram formats or image rendering.
- ▌ 11 Explore 2 · ai-driven-dev bundleExplore the current project across its tooling, context, and codebase. Use to survey what is installed, see what is available, or find which skill, agent, or rule fits a goal. Not for choosing the next step or running an item; it only points.
- ▌ 02 User Stories 2 · ai-driven-dev bundleProduces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.
- ▌ 08 Three Amigos 2 · ai-driven-dev bundleAssesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.
- ▌ 02 Check 2 · ai-driven-dev bundleStates what is in place — where measurement is allowed from, whether an identity is attached, where records land, whether the recorder is declared — then answers whether AIDD measurement is actually recording, one independently verifiable line per claim. Use when the user doubts a figure, sees no run file appear, wants proof the chain is working, or wants to know what is already configured. Not for turning measurement on or answering what a period cost.
- ▌ 03 Release Tag 2 · ai-driven-dev bundleCut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.
- ▌ 06 Product Brief 2 · ai-driven-dev bundleProduces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning.
- ▌ 02 Challenge 2 · ai-driven-dev bundleRethink just-completed work against an agreed plan, classifying findings as deal-breaker, suggestion, or correct, with a confidence score. Use to challenge or critically review recent work. Not for line-by-line style review or writing code.
- ▌ 02 Pull Request 2 · ai-driven-dev bundleCreate a draft pull or merge request from the current branch, in whatever VCS tool the project uses. Use when the user wants to open a pull or merge request. Not for committing, pushing, or merging a branch.
- ▌ 04 Issue Create 2 · ai-driven-dev bundleCreate an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue.
- ▌ 01 Bootstrap 2 · ai-driven-dev bundleDesign and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
- ▌ 01 Sdlc 2 · ai-driven-dev bundleAutonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for running one development step.
- ▌ 01 Brainstorm 2 · ai-driven-dev bundleClarify a vague product or technical intent through natural discovery. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.
- ▌ 04 Fact Check 2 · ai-driven-dev bundleVerify factual claims in a text against authoritative sources and rewrite it with footnote citations, hedging the unconfirmed. Use to fact-check, verify a claim, or cite sources on request. Not for judging code or clarifying requirements.
- ▌ 03 Shadow Areas 2 · ai-driven-dev bundleScan a markdown artifact (idea, stories, PRD, spec) for blind spots into a shadow report grouped by category and severity. Use to find gaps or what is missing in a written artifact. Not for interactive Q&A or code review.
- ▌ 02 Backlog 2 · ai-driven-dev bundleOrchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.
- ▌ 05 Rule Generate 2 · ai-driven-dev bundleGenerate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
- ▌ 08 Hook Generate 2 · ai-driven-dev bundleGenerate a hook, a handler that runs at a lifecycle event, across the host AI tools. Use when the user wants to create, scaffold, or refactor a hook, or automate an action at a lifecycle point. Not for other artifacts like skills or rules.
- ▌ 02 Project Memory 2 · ai-driven-dev bundleBuild the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
- ▌ 04 Skill Generate 2 · ai-driven-dev bundleGenerate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
- ▌ 06 Agent Generate 2 · ai-driven-dev bundleGenerate an agent across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor an agent, subagent or specialized role. Not for other artifacts like skills, rules, commands, hooks.
- ▌ 00 Async Dev 2 · ai-driven-dev bundleDrive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
- ▌ 03 Context Generate 3 · ai-driven-devRoute a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
- ▌ 07 Command Generate 2 · ai-driven-dev bundleGenerate a flat slash command across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a one-shot slash command. Not for multi-step skills or other artifacts like rules, agents, hooks.
- ▌
- ▌ Harden · ai-driven-devRe-read a diff for unvalidated input, swallowed errors and missing edge cases
- ▌
- ▌ Rollback · ai-driven-devRoll back a release of the ingest platform without losing in-flight batches. Use when a deploy has to be undone.
- ▌
- ▌
- ▌ Migrate External API · ai-driven-devPhased migration of a third-party API client — new client alongside the old, reads before writes, a disagreement metric before cutover. Use when replacing or upgrading a provider SDK.
- ▌ Tools · ai-driven-dev bundleDefines or modifies what the project targets, under src/contexts/tools/ — an AI/IDE tool profile, its build contract, the content-translation capability classes it composes (agents/skills/commands/rules/hooks), and its own native-plugin adapter. Use when adding a new AI or IDE tool, changing a tool's Has* capability intersection, adding or modifying a capability class, or declaring a tool's `aidd translate` build contract. Do NOT use for the canonical-to-native translation pipeline itself — use `translate`. Do NOT use for where plugin content comes from — use `distribution`. Do NOT use for manifest or install orchestration — use `framework`.
- ▌ Telemetry · ai-driven-devOwns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps records per machine. Use when adding a reader for another tool's transcript format, changing how a figure is attributed or reported, touching the sink or the identity store, or wiring a telemetry port. Do NOT use for what a tool declares about being measured — that is `kernel/measurement.ts`, read via the `tools` skill. Do NOT use for installing or removing the hook that writes the run journal into a project — that record belongs to `framework`.
- ▌ Translate · ai-driven-devBuilds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing `PluginContentTranslator`, adding a build strategy, or wiring a new tool into the build registry. Do NOT use for a tool's own profile, capability classes, or build contract — use `tools`. Do NOT use for where content is fetched from — use `distribution`. Do NOT use for manifest/install orchestration — use `framework`.
- ▌ 03 Prd · ai-driven-dev bundleGenerate a structured Product Requirements Document from a need, idea, or brainstorm, confirmed before save. Use when the user wants to draft or generate a PRD or product requirements. Not for user stories or a technical plan.
- ▌ 07 Epic · ai-driven-dev bundleProduces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
- ▌ 10 Task · ai-driven-dev bundleProduces or refines a backlog Task for bounded delivery work without independent user value. Use when the user wants to create, link, order, estimate, transition, or complete one. Not for User Stories, Spikes, Defects, or implementation.
- ▌ Distribution · ai-driven-devOwns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use `tools` or `translate`. Do NOT use for recording what got installed on a project — use `framework`.
- ▌ 10 Todo · ai-driven-dev bundleSplit the user prompt into independent todos and run one executor agent per todo in parallel, then report a minimal table. Use when the user says "todo" or asks to fan out a multi-part request into parallel implementations.
- ▌ 05 Spike · ai-driven-dev bundleProduces an evidence-bounded spike for an uncertainty blocking estimation, feasibility, or design. Use when the user wants to frame, investigate, resume, or conclude one. Not for general research or implementation.
- ▌ 01 Hello · ai-driven-dev bundleSmoke-test that confirms the aidd-ui plugin loads. Use when the user wants to verify the alpha aidd-ui plugin is installed and reachable. Not for real UI or UX design work.
- ▌ 09 Defect · ai-driven-dev bundleProduces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.