What problem does it solve?
Teams using the AI-DLC methodology frequently have documentation that is out of sync with actual implemented source and infrastructure code, leading to misalignment between planned and delivered work, wasted review cycles, and gaps in operational and verification knowledge.
Core Features & Use Cases
- Source-Aligned Doc Generation: Reads actual implementation files (Terraform, Python, JavaScript, etc.) before writing any construction documentation to ensure docs reflect what is built, not what was planned.
- Standardized Phase Structure: Follows official AI-DLC phase-to-folder mapping and per-document structure conventions for inception, construction, operations, and verification phases to maintain consistency across projects.
- Edge Case Handling: Supports retroactive documentation for already implemented work, append-only audit logging that matches existing project formats, doc index updates, and full bootstrapping for new AI-DLC projects.
- Use Case: For example, if your team just completed a cloud infrastructure unit in Terraform, this skill will generate the correct construction-phase docs (infrastructure design, NFR requirements, build instructions) based on the actual .tf files you wrote, not the original project plan.
Quick Start
Ask the AI to generate the operations-phase deployment runbook for the new authentication service you just deployed to production in your project's AI-DLC docs root.