aidlc

AIDLC (AI Development Life Cycle) orchestrator: reads work items (Jira/ADO/markdown), routes them through requirements, planning, implementation, review, QA and PR — across one repo or a multi-repo workspace, with or without a git remote, end to end. Stack-agnostic by design; language and framework expertise comes from stack packs.

52 skills · 9 agents · 1 MCP server · hooks

UI/UX pod that starts from whatever already exists. Screens in Figma → it ships the Figma MCP, extracts the spec and variables, builds to the design and gates on fidelity, with the jury offered rather than imposed. A brand design system in Figma → its variables and components become the project's tokens and vocabulary (workspace-wide), and the pod designs the screens within them, jury still gating. Neither → UX-narrative writer, Awwwards inspiration researcher, design-system owner, motion specialist, and a strict unbiased jury that renders the UI and gates on ≥9/10. New or existing projects, page or whole-app scope, honors brand references (logo/colors/fonts). Bundles the Figma and Playwright MCP servers it needs, so a backend-only workspace installs neither. Enabled by default; it only activates on UI items, so backend-only projects are unaffected.

8 skills · 7 agents · 2 MCP servers

Default web stack expertise for the AIDLC pipeline: TypeScript standards + strict tooling baseline (ESLint/Prettier/tsconfig/.gitattributes + optional husky/lint-staged) + enterprise project structure (scaffold + dependency-cruiser boundary gate) + the Node/TS CI half (templates, the npm gate, isolated-checkout dependency resolution, cross-platform lockfiles) + the Prettier auto-format hook, Next.js, NestJS, Postgres, MongoDB, DB migrations, Docker, API design.

10 skills · hooks

The Azure DevOps MCP server for AIDLC's ADO adapter. Optional — the adapter's `az boards`/`az rest` tier covers every operation and is what headless runs already use, so ADO works without this. Install it for the richer interactive tier; needs ADO_MCP_ORG in the launching shell.

1 MCP server

The Atlassian MCP server for AIDLC's Jira adapter. Required when workItems.source is "jira" — that adapter has no CLI fallback. Install only on Jira projects; core ships no tracker server, so a markdown or ADO workspace starts neither.

1 MCP server

A mod (Claude Code 2.1.287+) that shows AIDLC beside the chat: a line above the prompt with the runs in flight and anything waiting on you, a board pane for runs and the sprint, /aidlc-board with no model turn, a desktop notification when a sprint run needs you, the module you're changing and what uses it, this session's files and checks, each epic as a tree of its stories, tasks and bugs, and what each work item cost by phase (feeds /aidlc:insights). It draws what core's scripts report, calls no model and gates nothing; it writes only its git-ignored cost ledger and board copy. Optional: AIDLC works the same without it, which matters where an organization allows only its own mods.