skills.rest
zhaohuanke123
zhaohuanke123COMMUNITY
Explore all skills by this author →
GitHub

software-dev

Guide software projects through a 10-phase document-first lifecycle with Git checkpoints.

3|Updated Apr 9, 2026
Search Tags:#architecture#unit testing#software development#project scaffolding#git versioning#documentation gate#lifecycle workflow
One-click install
npx skills add https://github.com/zhaohuanke123/vanko-skill --skill software-dev-zhaohuanke123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-dev
Source: https://github.com/zhaohuanke123/vanko-skill/tree/main/skills/software-dev
Command: npx skills add https://github.com/zhaohuanke123/vanko-skill --skill software-dev-zhaohuanke123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

software-dev helps you reliably take an idea from problem definition to working software by forcing a disciplined, documentation-first lifecycle with verification gates and durable project artifacts that let work continue across conversations.

Core Features & Use Cases

  • 10-phase, phase-gated delivery: Moves through problem definition, requirements, planning, architecture, detailed design, coding, unit testing, integration, system testing, and delivery outputs.
  • Documentation Gate for behavioral changes: Ensures code edits happen only after the governing requirements/design/architecture docs are updated for the requested behavior.
  • Durable context for resuming: Produces and maintains PROJECT.md, CLAUDE.md, AGENTS.md, and WORKFLOW.md so future agents can pick up without losing the workflow.
  • Git-required checkpoints: Records meaningful milestones and releases with commits/tags and supports rollback notes in version history.
  • Traceability and lessons learned: Keeps version history and lessons in structured docs, ensuring docs/code/tests/README stay consistent.

Quick Start

Tell your agent: "Start phase-gated development with software-dev and help me build the app I described, keeping documentation updated and verified through tests, then deliver a runnable project with PROJECT.md, CLAUDE.md, AGENTS.md, WORKFLOW.md, and version history."

Frequently Asked Questions about software-dev

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

FAQPage Schema
How do I enforce a documentation gate for software development before code changes?▼

A documentation gate ensures code edits happen only after governing requirements, design, and architecture docs are updated. This enforces a document-first lifecycle where behavioral changes are planned and verified before implementation begins.

What is phase-gated software delivery and how does it structure project workflows?▼

Phase-gated software delivery moves projects through 10 phases: problem definition, requirements, planning, architecture, detailed design, coding, unit testing, integration, system testing, and delivery. Each phase must be completed before advancing to ensure verified artifacts and durable context.

Can I use Git versioning to checkpoint changes during a software development lifecycle?▼

Yes, Git-based checkpointing records meaningful milestones and releases with commits and tags. It supports rollback notes in version history, ensuring changes are traceable and previous project states can be restored during development.

How do I maintain durable project context for resuming software work across conversations?▼

Durable project context is maintained by producing PROJECT.md, CLAUDE.md, AGENTS.md, and WORKFLOW.md files. These artifacts capture workflow state, architecture, and lessons learned so future agents can resume development without losing context.

Does phase-gated development work for small or demo software projects?▼

Yes, this phase-gated lifecycle applies to building, continuing, debugging, or changing small and demo software projects. It provides disciplined planning, architecture, implementation, and testing tailored for projects requiring verified delivery artifacts.

What is the best way to keep documentation, code, tests, and README consistent throughout a project?▼

Traceability and lessons learned are maintained by keeping version history and lessons in structured docs, ensuring documentation, code, tests, and README stay reconciled. Strict documentation gates enforce this consistency before any code modifications proceed.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

speckit-git-initialize

Initialize a Git repository with an initial commit in the current directory.

Community
Intermediate
jubscodesjubscodes
49

gspdev-publish

Bump version numbers, update changelogs, and prepare npm release artifacts.

Community
Advanced
noundernounder
3

effect-testing

Test Effect.ts success and failure paths with deterministic concurrency handling.

Community
Intermediate
jikimejikime
5

jikime-workflow-poc

Orchestrate phase-based development workflows for greenfield features using a POC-First methodology.

Community
Advanced