software-development

Orchestrates a gated pipeline from intent spec through implementation, logging, and documentation.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/deriye/.agents-work --skill software-development-deriye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-development
Source: https://github.com/deriye/.agents-work/tree/main/skills/software-development
Command: npx skills add https://github.com/deriye/.agents-work --skill software-development-deriye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code changes made without specs, plans, or logs lead to drift between documentation and implementation, untracked behavior changes, and stale docs. This Skill enforces a gated software-development lifecycle so every code change—feature, bug fix, or refactor—produces a consistent record of intent, terminology, domain model, plan, and log. ## Core Features & Use Cases - Gated 13-step pipeline: Runs AGENTS.md setup, intent spec (via isdd), drift checks, terminology, domain model, plan, design (via huashu-design), implementation, log, README, architecture/mechanisms, and final compliance review. - User-controlled steps: Requires confirmation before use and before each step; explicit user skips override gates and are recorded in the log. - Delegate orchestration: Coordinates isdd, domain-model, huashu-design, generate-tutorials, and coding-best-practices skills, plus graphify for token-efficient repo exploration. - Use Case: When asked to fix a bug or add a feature, load this Skill first; it walks you through spec verification, planning, and design before any code is written, then records the log and updates README afterward. ## Quick Start Ask the agent to load the software-development skill before making any code change, then confirm each pipeline step as it is presented.

Frequently Asked Questions about software-development

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

FAQPage Schema
How do I enforce a spec-before-code workflow for AI coding agents?▼

Load this skill before any code-touching request; it runs a gated pipeline where intent spec, terminology, domain model, plan, and design must be confirmed before implementation. Gates block code by default, and each step requires explicit user confirmation or skip.

What is the software-development skill pipeline order?▼

The pipeline runs Steps 0-7 before code: AGENTS.md, intent spec, intent drift check, terminology, domain model, implementation plan, design, and plan drift check. Step 8 implements code and tests, then Steps 9-12 write the log, README, architecture/mechanisms, and a final AGENTS.md review.

Does the pipeline apply to small bug fixes?▼

Yes, bug fixes are not exempt and follow the same pipeline with lighter docs. The spec check is usually no drift, the domain model unchanged, but a plan and log entry are still required for every fix.

Can I skip steps in the development pipeline?▼

Yes, the user controls every step and can confirm, skip, or modify each one. An explicit skip overrides the mandatory gate rules and is recorded in the Step 9 log so the pipeline record stays honest.

Where does the skill store specs, plans, and logs?▼

Artifacts live under a configurable directory defaulting to docs/, including docs/features/<feature>/spec.md and plan.md, docs/terminology.md, docs/domain-model/, and docs/logs/. AGENTS.md, README.md, and a gitignored tmp/ stay at the repo root.

When should I not use this gated development workflow?▼

The skill is designed for any code-touching change, so there is no exempt scenario within a repo that adopts it. It is not suited for non-code tasks like pure writing or research, and it never runs git commands unless the developer explicitly asks.