AI-Driven Life Cycle (AI-DLC) adaptive workflow steering rules for AI coding agents
About the project
AI-DLC Workflows is a reusable software-development lifecycle that guides AI coding agents through staged engineering work and human approval gates. Teams use it to run structured, reviewable development processes across several coding-agent environments, and the catalogue entries are its agents, skills, rules, MCP integrations, and instructions.
Index the team's own documents — PDFs, Word files, Markdown, plain text — into a per-space catalog the AI-DLC agents can cite. Wraps aidlc-knowledge.ts: onboard, sync, list, show, associate, dissociate, rebind, summarize. Every catalog row is written by the tool under a workspace lock; this skill never edits the…
Generate a comprehensive handover document at workflow close so the team can own, operate, and continue the system without re-running the workflow. Stage/phase/learning counts come from {{INVOKE}} engine runtime summary; prose comes from the artefacts. Writes OUTCOMES.md but never mutates workflow state or emits audit…
Print a structured session narrative for stakeholders who weren't in the room. Numbers (stage counts, phase rollup, duration) come from {{INVOKE}} engine runtime summary; prose comes from the audit trail and artefacts. Renders to the terminal only — writes no file, never mutates workflow state, never emits audit…
Read-only session cost view. Prints deterministic aggregates for the current workflow — duration, stage outcomes, memory entries, sensor firings, learnings captured — sourced entirely from {{INVOKE}} engine runtime summary. Never mutates workflow state, never emits audit events, never writes files.
AI-DLC. Start, resume, or manage an AI-driven development lifecycle. Scopes are defined one file per scope under .claude/scopes/; run {{INVOKE}} engine orchestrate help for the authoritative list and descriptions. Utilities, each an argument to {{INVOKE}} engine orchestrate next and never a command of its own…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: