sdlc

Orchestrate TDD, test-runner checks, and commit preparation from feature specs.

6|1|Updated Mar 5, 2026

Search Tags:#automation #workflow #tdd #sdlc #software-development #test-runner

Ready to run

npx skills add https://github.com/pwv-vc/agentcribs-community --skill sdlc-pwv-vc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdlc
Source: https://github.com/pwv-vc/agentcribs-community/tree/main/resources/tearsheets/arsenal/dot-claude/skills/sdlc
Command: npx skills add https://github.com/pwv-vc/agentcribs-community --skill sdlc-pwv-vc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates end-to-end feature development by orchestrating TDD, test-runner checks, and commit preparation, eliminating fragmented manual steps.

Core Features & Use Cases

Orchestrates TDD with a provided spec/plan to drive development.
Runs linting, type checks, and tests via the test-runner skill.
Identifies modified files related to the user's request.
Prepares git commit commands for manual execution, while explicitly avoiding automatic commits or pushes.
Use Case: Apply when a user provides a feature spec and wants an end-to-end automated workflow.

Quick Start

Use the SDLC skill to implement the provided spec by running the TDD skill, then the test-runner skill, and finally prepare commit commands for manual execution.

Frequently Asked Questions about sdlc

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

FAQPage Schema

How do I automate TDD workflows from a feature spec to validated changes?▼

Automate TDD workflows by using an orchestration skill to coordinate test-driven development, run linting and type checks, and identify modified files. This end-to-end software development lifecycle workflow processes feature specs to drive validated changes with guardrails.

How do I prepare git commit commands for manual execution after running tests?▼

Prepare git commit commands by identifying modified files related to the feature spec and generating executable commit instructions. The workflow explicitly avoids automatic commits or pushes, outputting prepared commands for manual execution to maintain developer control.

What is the best way to orchestrate test-runner checks and TDD in one workflow?▼

The best way to orchestrate test-runner checks and TDD is using a coordinated software development lifecycle skill. It guides the workflow from spec to validated changes by running TDD first, then executing linting, type checks, and tests via the test-runner.

Can I use an automated SDLC workflow without automatic commits or pushes?▼

Yes, you can use an automated SDLC workflow with guardrails that explicitly avoid automatic commits or pushes. The workflow prepares git commit commands and identifies modified files, outputting prepared commands for manual execution to ensure developer oversight.

Does the automated software development lifecycle workflow work with feature-spec driven requests?▼

Yes, the automated software development lifecycle workflow is designed for feature-spec driven requests. It applies TDD orchestration and test-runner checks to the provided spec, guiding the workflow from initial spec to validated changes and identified modified files.

Why does the SDLC workflow output prepared commands instead of committing directly?▼

The SDLC workflow outputs prepared commands to enforce guardrails that avoid automatic commits or pushes. This design eliminates fragmented manual steps during TDD and test-runner execution while ensuring developers retain control over the final git commit action.