sdlc

Orchestrate TDD, test-runner, and commit command preparation from a feature spec.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cncorp/arsenal --skill sdlc-cncorp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/sdlc
Command: npx skills add https://github.com/cncorp/arsenal --skill sdlc-cncorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the software development lifecycle workflow by orchestrating a TDD-driven specification, test-runner execution, file identification, and git-commit command preparation for user review.

Core Features & Use Cases

  • TDD-driven spec handling: invoke the TDD skill with a spec/plan.
  • Test-Runner coordination: executes lint, type checks, and tests.
  • Commit commands preparation: identifies modified files and formats commit commands for user review.
  • Use Case: When you have a feature spec, SDLC skill returns a set of commands to review and apply manually.
  • Note: It does not perform git commits or pushes.

Quick Start

Run the SDLC skill with your feature spec to auto-run TDD and test-runner, then prepare user-reviewable commit commands.

Frequently Asked Questions about sdlc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate my software development workflow with testing and commits?

SDLC automation orchestrates test-driven development, runs linting and type checks, identifies modified files, and prepares git commands for review—no automatic commits. Provide a feature spec to trigger the full workflow end to end.

What's the difference between manual testing and a TDD-first workflow?

TDD-first workflow writes tests before code, then validates against lint, type checkers, and test runners in one pass. This catches errors early and ensures specs drive implementation, unlike manual testing after code is written.

Can I use this for CI pipeline setup without pushing to git automatically?

Yes. SDLC prepares all commit commands to a file for your review and manual execution. You control when and what gets pushed; the Skill orchestrates test-runner checks and file identification only.

Do I need to run lint, type checking, and tests separately?

No. SDLC coordinates all three—lint, type checks, and tests—in a single execution after TDD. Results and modified files are identified together, reducing manual context switching.

What happens if tests fail during the SDLC workflow?

The test-runner output is logged and reviewed before commit commands are prepared. Failed tests block command generation, letting you fix issues before the prep phase completes.

How do I review changes before committing with SDLC?

SDLC identifies all modified files related to your request and saves formatted git-commit commands to tmp/git-commands.txt. Review the file list and commands, then execute them manually at your pace.