sdlc

You automate the SDLC workflow by orchestrating planning, implementation, testing, review, and deployment through structured quality gates. This skill generates a TodoWrite-style plan to capture tasks, risks, and dependencies before coding to enforce disciplined practices automatically.

Planning-first governance is an SDLC protocol that generates a TodoWrite-style plan to capture tasks, risks, and dependencies before coding begins. It ensures disciplined software development practices are followed automatically across the entire project lifecycle.

You keep documentation synchronized by enforcing governance checks that update feature docs, CLAUDE.md, TESTING.md, and ARCHITECTURE.md alongside code changes. This ensures project documentation stays consistent throughout the development lifecycle.

Yes, you need a repository-contained SKILL.md file with name and description frontmatter to enable deterministic tasks and context during activation. Optional fields, operational body, and resources like scripts or references can further enhance context-aware execution.

Yes, you can use this SDLC workflow automation for features, bug fixes, refactors, testing, release, and deployment. It coordinates the entire process with structured gates and checklists to ensure quality across all software engineering tasks.

The best way to enforce quality gates is by orchestrating a structured SDLC checklist that coordinates planning, testing, review, and release phases. This approach ensures disciplined practices are followed automatically before deployment proceeds.