aicdd

Plugin aicdd from marketplace aicdd in jordanschwartz/AICDD. Commands read from the repo's manifest — 1 month ago.

Skills (15)

• bootstrapper

  Construct the initial Capability Graph for an existing software system - discover its enduring business capabilities, establish capability boundaries, and document system understanding as organizational knowledge rather than implementation detail. Writes project-context/manifest.json, capabilities.j

• capability-author

  Map a hardened spec (or PRD) to the capability graph and author one Capability Change Request (CCR) per impacted capability — what each capability must become. Performs Capability Discovery (extend existing vs. new); does NOT decompose work into tasks or write code. Tags each CCR with the plain-lang

• enricher

  Improve the quality and completeness of an existing Capability Graph - deepen persistent system understanding without changing system behavior and without creating, removing, or renaming capabilities. Updates existing capability artifacts under project-context/ in place so future agents need less re

• historical-prd-discovery

  Analyze historical product artifacts - PRDs, feature specs, design docs, RFCs, ADRs, release notes, user stories - to extract recurring business concepts, terminology, intent, and product evolution rather than summarizing individual documents. Gathers from the repo AND, when configured, a tracker (J

• implementer

  Execute assigned implementation tasks from a Capability-Driven Delivery (CDD) execution plan, instantiating an Agent Team directly from assignments.md. Use this skill whenever the user references an execution-plan.md, assignments.md, Capability files, a Capability Graph, an initiative folder, or CDD

• inquiry

  Help a user understand the current system before defining a change - answer what is true today about existing capabilities, behavior, business rules, constraints, and gaps. Treats the Capability Graph under project-context/ as the primary source of understanding, exploring the repository only when p

• map-refresh

  Re-check an existing capability map and bring it back up to date — THE single command for "is my map still true?" Two tiers — incremental (diff since each capability's watermark, re-verify only what moved) for routine freshness, and full re-eval (re-discover + red-team the whole map) as the periodic

• map-review

  Verify a Capability Graph is trustworthy AND complete before anything relies on it — an adversarial "disprove it" pass over each capability's stated guarantees, an independent second read, and a triangulated completeness check that hunts for MISSING capabilities. Read-only: produces per-capability v

• planner

  Transform authored Capability Change Requests (CCRs) into a deterministic engineering execution plan - analyze repository impact, determine dependencies, and break the work into atomic, parallelizable tasks without writing production code. Writes execution-plan.md for the initiative. Capability disc

• prd-writer

  Turn an informed product decision into a precise, implementation-agnostic declaration of desired behavior - answer what should become true by combining current-state understanding from Capability Inquiry, industry and incumbent discovery, and human intent. Writes project-context/initiatives/[slug]/p

• project-discovery

  Develop a high-level understanding of a software system before Capability Discovery begins - what it is, why it exists, its major architectural characteristics, and its business domain, without decomposing it into capabilities. Writes project-context/project.md and manifest.json as foundational cont

• repository-inventory

  Create a structured inventory of the repository - a searchable map of what exists (directories, source, configuration, build and infrastructure files, APIs, database schema, tests, docs) without explaining why it exists or how it behaves. Writes project-context/repository-inventory.md as a navigatio

• reviewer

  Validate implementation against planning intent - check capability mapping, CCR compliance, task completion, behavioral correctness, architectural consistency, test coverage, and regression risk. Produces review-report.md as analysis for humans, who remain responsible for approval. Runs at the VERIF

• steward

  Synchronize the Capability Graph with approved implementation - update only the behavior, architecture, implementation, verification, history, dependencies, and AI-context sections affected by the change, never modifying production code. Updates existing capability files under project-context/ so or

• techlead

  The Engineering Lead role — turn an approved execution-plan.md into an assignments.md. Infer the smallest effective agent team, assign every execution task to exactly one agent, respect dependencies, and maximize safe parallel execution — without redesigning or decomposing the work. Runs at the ASSI

Similar plugins