adopt-adrWrite retroactive ADRs for the decisions the code already embodies, one at a time behind approval, citing the code and leaving the rationale for a person. Use after /aidlc:adopt when docs/adr/ is empty.
adopt-applyApply an approved adoption profile — writes aidlc.config.json, the CLAUDE.md facts and the git-workflow rule behind a full diff and your approval, merging with what people wrote. Use after /aidlc:adopt, or to re-apply an updated profile.
adopt-backlogFile the debt an adoption scan found (missing gates, untested critical paths, end-of-life dependencies, TODO clusters) as deduplicated items with acceptance criteria, each shown before it is created. Use after /aidlc:adopt.
adoptRead-only scan of an existing workspace (one repo or several) into an evidence-backed profile — topology, stack, real gates, CI, git conventions, runtime constraints, undocumented decisions and debt. Re-run it to report drift. Use when adopting AIDLC on code that already exists.
agent-contractWhat every AIDLC subagent owes its orchestrator — the finish contract, the report-back shape and the tool-restriction policy. Load when writing, reviewing or scaffolding an agent.
architectureADR triggers and format, and the explore-before-deciding checklist. Load when planning a medium-or-larger work item or making a hard-to-reverse technical decision.
bootstrapPlan a batch of requirements into the tracker in one reviewed pass — a whole backlog from a requirements document, or a document of new features for a product that already ships. Epics to tasks with acceptance criteria, team assignment and sprints. Use instead of /aidlc:intake for more than one requ
brainThe project brain (.aidlc/brain/) — a sourced page per module, plus user types, flows and vocabulary. Load before explaining, planning or changing a module, when taking over or handing over one, or after learning how part of the product works.
ceremonyThe four process tiers (answer, direct, tracked, full) and how to pick one. Load before deciding whether a request needs a work item, a branch or a PR.
ci-cdCI authoring and red-check diagnosis for GitHub Actions and Azure Pipelines, any stack. Load when changing workflow YAML or diagnosing failing checks; on a Node repo, together with aidlc-stack-web:ci-web.
code-reviewThe review checklist, severity taxonomy and finding format for the verify phase. Load when reviewing a pipeline diff against acceptance criteria and standards.
debuggingThe bug protocol — reproduce, failing test, root cause, minimal fix, regression sweep. Load for any bug item or when diagnosing a failure during a run.
doAIDLC's front door for any prompt — it grounds in the project (config, runs, backlog, ADRs), then answers or acts at the lightest ceremony that fits. Use for fit and opinion questions ("should we use X?"), investigations, small fixes (a typo, a rename) and plain "build this / fix this" requests that
docs-writingWhat to update per change type (README, CHANGELOG, API docs) and how to write it. Load when updating project documentation for a work item.
doctorRead-only diagnosis of an AIDLC workspace (config, plugins, permissions, hooks, run files, tracker and CLI auth), each problem with its fix. Use when /aidlc:* commands are missing or misbehave, a run blocks on permissions, or after installing or updating the plugins.
dogfoodLog friction with the AIDLC plugin itself (wrong or missing guidance, workarounds, skill or template bugs, not project bugs) to a local inbox for its maintainer. Use when the plugin is the problem, or on /aidlc:dogfood.
factsProject facts (.aidlc/facts.md) — dated operational truths the pipeline keeps relearning. Read before diagnosing an environment failure or briefing an implementer; add one whenever a run learns something the hard way.
git-workflowBranch naming, conventional commits, push and PR creation (GitHub via gh, Azure Repos via az). Load when branching, committing or opening a pull request for a work item.
groomBacklog refinement — fix weak acceptance criteria, size items, flag blockers and stale items, propose splits and priority changes. Use when asked to groom, refine or clean up the backlog.
initScaffold the AIDLC project template into the current repository — CLAUDE.md, permissions, aidlc.config.json, rules, backlog structure, run-state folders. Use when adopting the AIDLC framework in a new or existing project.
insightsRead-only outcome metrics for this workspace's pipeline — time to done, fix cycles, findings by source, month by month. Use when asked how the pipeline is doing, whether a change helped, where time goes, or what keeps coming back in review.
intakeTurn a plain-language requirement into backlog items with acceptance criteria in the active tracker, deduplicated against the board. Use when the user describes something to build or fix that is not yet a work item.
journalThe workspace journal (.aidlc/journal.md), one line per event, read back at session start. Load when finishing a command that changed something, or to see what has been happening here.
learnBuild or refresh the project brain — map the modules from the code, read one deeply, or refresh pages the code has moved past. Use when taking over a module, starting AIDLC on an existing project, or when brain pages are behind the code.
maintenanceDependency updates, deprecation sweeps and safe refactors. Load for maintenance items, dependency updates or scheduled maintenance.
nextPick the highest-priority ready item and run it through the pipeline. Use when asked to work on the next item, pick up work or continue with the backlog.
planningDecomposition, sizing and dependency detection for AIDLC plans. Load when writing an implementation plan or sizing and sequencing backlog items.
promotePromote a project-local skill or agent into the shared AIDLC marketplace plugin — validate, generalize, package and open a PR against the marketplace repo. Use when a local extension has proven reusable (reuseCount >= 2) and should become available to all projects.
releaseCut a release — semver from conventional commits, changelog, tag and notes for GitHub or Azure DevOps. Use for release items or when asked to cut, prepare or tag a release.
removeRemove AIDLC from this project — delete its own files, revert only what it merged, keep everything the team wrote. Shows the plan first and verifies the project's files are back to how they were. The plugin itself goes with /plugin uninstall.
replanRe-sequence not-yet-started work into waves when priorities change ("checkout before search", "all backend first", a revised spec), saved as the plan /aidlc:next and /aidlc:sprint follow. Use when asked to re-plan, re-prioritize, re-sequence or re-phase.
repoDeclare and bootstrap a repo in a poly workspace — add it to repos[], git-init it and make a base commit. Use when work references a repo that is not declared yet.
requirementsThe acceptance-criteria bar, INVEST checklist and assumption-logging protocol. Load when validating, refining or writing acceptance criteria.
researchThe spike protocol — sharpen the question, gather cited evidence, verify the load-bearing claims, deliver a decision. Load for a spike item or a technical choice mid-run.
reuseUse BEFORE writing or planning new code (a feature, screen, component, hook, helper, client, type or test) — find what already exists and extend it instead of writing a second one, and catch what a branch duplicated. Load for any implement, plan or review task, including plain requests like "add X t
review-feedbackWork a reviewer's PR comments like pipeline findings — fetch the unresolved threads (GitHub or Azure Repos), fix them through the fix cycle, push and reply on each. Use when a PR has review comments to address.
run-stateThe run-file format (.aidlc/runs/<ID>.md) and checkpoint/resume protocol. Load when creating, updating, resuming or archiving a pipeline run.
runRun one work item (epic, story, task, bug or spike) through the full AIDLC pipeline — fetch, requirements, plan, implement, review + QA with fix cycles, PR, tracker update. Resumable. Use when asked to work on, implement, fix or deliver a work item by ID.
scaffold-agentCreate a project-local subagent from the AIDLC template. Use only when a role needs its own context, tool surface or independent judgment, and no existing agent or skill covers it.
scaffold-skillCreate a reusable project-local skill from the AIDLC template. Use when a needed procedure, convention or integration exists in no installed plugin or local skill.
securityThe security review procedure — OWASP-oriented diff review, dependency audit, secret patterns, authz reasoning. Load for a security pass on a work item or a dependency audit.
sprintRun several independent work items in parallel, each as a Claude Code background session — routed per repo from the control plane in poly, or in isolated git worktrees in mono — and aggregate progress into one board that says which run needs you. Use when asked to work multiple backlog items at once
statusThe AIDLC dashboard — active runs with phase, branch and PR, plus ready backlog items. Use when asked about AIDLC progress, active runs or what's next.
studyWrite the business study of the product from the project brain — users, modules, flows, data, decisions, intended versus built, open questions, every claim sourced. Use when a project ends, for a handover, or when asked for a document that explains the whole product.
syncReconcile project-local AIDLC extensions against the installed plugin versions — detect promoted skills now shadowed by the plugin, remove the local fork, and report drift. Use after plugin updates or when local and plugin skills may overlap.
testingTest policy — the pyramid, what to test per change type, coverage and flaky tests. Load when writing or evaluating tests in the verify phase.
undoReverse an AIDLC run — close its PR and delete its branch, or revert it through a new PR if it merged — and put the board back. Never rewrites history; shows the plan first. Use when a run should not have happened.
upgradeCatch a project's AIDLC files up with the installed plugin — config and permission-rule migrations, rules and CLAUDE.md drift, every change shown first. Use after /plugin marketplace update, or when /aidlc:doctor says the config is old.
wi-adoWork-item adapter for Azure DevOps Boards (MCP server, az CLI fallback). Load when workItems.source is "ado".
wi-jiraWork-item adapter for Jira (Atlassian MCP server). Load when workItems.source is "jira".
wi-markdownWork-item adapter for the markdown backlog (backlog/). Load when workItems.source is "markdown".
work-itemsThe canonical WorkItem schema, adapter contract and tracker routing. Load whenever reading or updating epics, stories, tasks, bugs or spikes in any tracker.