all publishers

ai-driven-dev

@ai-driven-dev source repo

125 published skills · page 1 of 2

  1. ▌
    00 Async Dev · ai-driven-dev bundle
    Drive 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.
    559 repo stars
  2. ▌
    01 Brainstorm · ai-driven-dev bundle
    Clarify 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.
    559 repo stars
  3. ▌
    02 Backlog · ai-driven-dev bundle
    Orchestrates 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.
    559 repo stars
  4. ▌
    05 Rule Generate · ai-driven-dev bundle
    Create, 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.
    559 repo stars
  5. ▌
    06 Agent Generate · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  6. ▌
    01 Sdlc · ai-driven-dev bundle
    Orchestrates 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.
    559 repo stars
  7. ▌
    00 Init · ai-driven-dev bundle
    Turn 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.
    559 repo stars
  8. ▌
    01 Commit · ai-driven-dev bundle
    Create 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.
    559 repo stars
  9. ▌
    12 Cook · ai-driven-dev bundle
    Manages 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.
    559 repo stars
  10. ▌
    07 Refactor · ai-driven-dev bundle
    Improve 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.
    559 repo stars
  11. ▌
    02 Implement · ai-driven-dev bundle
    Write 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.
    559 repo stars
  12. ▌
    04 Audit · ai-driven-dev bundle
    Audit 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.
    559 repo stars
  13. ▌
    08 Debug · ai-driven-dev bundle
    Reproduce 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.
    559 repo stars
  14. ▌
    03 Assert · ai-driven-dev bundle
    Assert 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.
    559 repo stars
  15. ▌
    05 Review · ai-driven-dev bundle
    Reviews 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.
    559 repo stars
  16. ▌
    06 Test · ai-driven-dev bundle
    Write 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.
    559 repo stars
  17. ▌
    01 Plan · ai-driven-dev bundle
    Turn 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.
    559 repo stars
  18. ▌
    Test · ai-driven-dev bundle
    Holds 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`).
    559 repo stars
  19. ▌
    Framework · ai-driven-dev bundle
    Owns 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`.
    559 repo stars
  20. ▌
    04 Spec · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  21. ▌
    01 Usage · ai-driven-dev bundle
    Answer 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.
    559 repo stars
  22. ▌
    01 Acceptance QA · ai-driven-dev bundle
    Validate 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.
    559 repo stars
  23. ▌
    Resolve Conflict · ai-driven-dev bundle
    Resolves 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.
    559 repo stars
  24. ▌
    10 Batch · ai-driven-dev bundle
    Split 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.
    559 repo stars
  25. ▌
    05 Improve · ai-driven-dev bundle
    Reads 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.
    559 repo stars
  26. ▌
    Release Video · ai-driven-dev bundle
    Plans 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.
    559 repo stars
  27. ▌
    Test 2 · ai-driven-dev bundle
    Holds 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`).
    559 repo stars
  28. ▌
    Tools 2 · ai-driven-dev bundle
    Defines 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`.
    559 repo stars
  29. ▌
    Framework 2 · ai-driven-dev bundle
    Owns 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`.
    559 repo stars
  30. ▌
    Telemetry 2 · ai-driven-dev
    Owns 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`.
    559 repo stars
  31. ▌
    Translate 2 · ai-driven-dev
    Builds 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`.
    559 repo stars
  32. ▌
    03 Prd 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  33. ▌
    04 Spec 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  34. ▌
    07 Epic 2 · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  35. ▌
    10 Task 2 · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  36. ▌
    Distribution 2 · ai-driven-dev
    Owns 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`.
    559 repo stars
  37. ▌
    01 Plan 2 · ai-driven-dev bundle
    Turn 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.
    559 repo stars
  38. ▌
    06 Test 2 · ai-driven-dev bundle
    Write 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.
    559 repo stars
  39. ▌
    10 Todo 2 · ai-driven-dev bundle
    Split 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.
    559 repo stars
  40. ▌
    05 Spike 2 · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  41. ▌
    01 Hello 2 · ai-driven-dev bundle
    Smoke-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.
    559 repo stars
  42. ▌
    04 Audit 2 · ai-driven-dev bundle
    Audit 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.
    559 repo stars
  43. ▌
    08 Debug 2 · ai-driven-dev bundle
    Reproduce 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.
    559 repo stars
  44. ▌
    09 Defect 2 · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  45. ▌
    03 Assert 2 · ai-driven-dev bundle
    Assert 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.
    559 repo stars
  46. ▌
    05 Review 2 · ai-driven-dev bundle
    Review 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.
    559 repo stars
  47. ▌
    01 Commit 2 · ai-driven-dev bundle
    Create 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.
    559 repo stars
  48. ▌
    12 Cook 2 · ai-driven-dev bundle
    Manage project recipes/how-to sheets by listing, creating, updating, researching, or applying a recipe. Use for recipe, cook, /cook, list, new, update, research, apply.
    559 repo stars
  49. ▌
    07 Refactor 2 · ai-driven-dev bundle
    Improve 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.
    559 repo stars
  50. ▌
    09 For Sure 2 · ai-driven-dev bundle
    Run 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.
    559 repo stars
  51. ▌
    10 Learn 2 · ai-driven-dev bundle
    Capture 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.
    559 repo stars
  52. ▌
    02 Implement 2 · ai-driven-dev bundle
    Write 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.
    559 repo stars
  53. ▌
    00 Repo Init 2 · ai-driven-dev bundle
    Initialize 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.
    559 repo stars
  54. ▌
    11 Browser QA 2 · ai-driven-dev bundle
    Run 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.
    559 repo stars
  55. ▌
    01 Ticket Info 2 · ai-driven-dev bundle
    Retrieve 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.
    559 repo stars
  56. ▌
    00 Init 2 · ai-driven-dev bundle
    Turns 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.
    559 repo stars
  57. ▌
    01 Cost 2 · ai-driven-dev bundle
    Answers 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.
    559 repo stars
  58. ▌
    00 Onboard 2 · ai-driven-dev bundle
    Guide 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.
    559 repo stars
  59. ▌
    09 Mermaid 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  60. ▌
    11 Explore 2 · ai-driven-dev bundle
    Explore 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.
    559 repo stars
  61. ▌
    02 User Stories 2 · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  62. ▌
    08 Three Amigos 2 · ai-driven-dev bundle
    Assesses 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.
    559 repo stars
  63. ▌
    02 Check 2 · ai-driven-dev bundle
    States 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.
    559 repo stars
  64. ▌
    03 Release Tag 2 · ai-driven-dev bundle
    Cut 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.
    559 repo stars
  65. ▌
    06 Product Brief 2 · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  66. ▌
    02 Challenge 2 · ai-driven-dev bundle
    Rethink 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.
    559 repo stars
  67. ▌
    02 Pull Request 2 · ai-driven-dev bundle
    Create 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.
    559 repo stars
  68. ▌
    04 Issue Create 2 · ai-driven-dev bundle
    Create 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.
    559 repo stars
  69. ▌
    01 Bootstrap 2 · ai-driven-dev bundle
    Design 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.
    559 repo stars
  70. ▌
    01 Sdlc 2 · ai-driven-dev bundle
    Autonomously 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.
    559 repo stars
  71. ▌
    01 Brainstorm 2 · ai-driven-dev bundle
    Clarify 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.
    559 repo stars
  72. ▌
    04 Fact Check 2 · ai-driven-dev bundle
    Verify 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.
    559 repo stars
  73. ▌
    03 Shadow Areas 2 · ai-driven-dev bundle
    Scan 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.
    559 repo stars
  74. ▌
    02 Backlog 2 · ai-driven-dev bundle
    Orchestrates 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.
    559 repo stars
  75. ▌
    05 Rule Generate 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  76. ▌
    08 Hook Generate 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  77. ▌
    02 Project Memory 2 · ai-driven-dev bundle
    Build 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.
    559 repo stars
  78. ▌
    04 Skill Generate 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  79. ▌
    06 Agent Generate 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  80. ▌
    00 Async Dev 2 · ai-driven-dev bundle
    Drive 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.
    559 repo stars
  81. ▌
    03 Context Generate 3 · ai-driven-dev
    Route 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.
    559 repo stars
  82. ▌
    07 Command Generate 2 · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  83. ▌
    Plan · ai-driven-dev
    Split a request into independent tasks, one worktree each
    559 repo stars
  84. ▌
    Harden · ai-driven-dev
    Re-read a diff for unvalidated input, swallowed errors and missing edge cases
    559 repo stars
  85. ▌
    Check Task · ai-driven-dev
    Run the project assertions and return a binary verdict
    559 repo stars
  86. ▌
    Rollback · ai-driven-dev
    Roll back a release of the ingest platform without losing in-flight batches. Use when a deploy has to be undone.
    559 repo stars
  87. ▌
    Add Endpoint · ai-driven-dev
    Procedure — add an endpoint
    559 repo stars
  88. ▌
    Schema Migration · ai-driven-dev
    Procedure — schema migration
    559 repo stars
  89. ▌
    Migrate External API · ai-driven-dev
    Phased 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.
    559 repo stars
  90. ▌
    Tools · ai-driven-dev bundle
    Defines 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`.
    559 repo stars
  91. ▌
    Telemetry · ai-driven-dev
    Owns 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`.
    559 repo stars
  92. ▌
    Translate · ai-driven-dev
    Builds 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`.
    559 repo stars
  93. ▌
    03 Prd · ai-driven-dev bundle
    Generate 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.
    559 repo stars
  94. ▌
    07 Epic · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  95. ▌
    10 Task · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  96. ▌
    Distribution · ai-driven-dev
    Owns 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`.
    559 repo stars
  97. ▌
    10 Todo · ai-driven-dev bundle
    Split 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.
    559 repo stars
  98. ▌
    05 Spike · ai-driven-dev bundle
    Produces 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.
    559 repo stars
  99. ▌
    01 Hello · ai-driven-dev bundle
    Smoke-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.
    559 repo stars
  100. ▌
    09 Defect · ai-driven-dev bundle
    Produces 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.
    559 repo stars