dev-discipline

Generate DEV-SPEC.md codifying code standards, commit protocol, review criteria, and debt management at .planning/DEV-SPEC.md.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill dev-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-discipline
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/dev-discipline
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill dev-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a formal working contract for software teams by documenting the required development standards, workflows, and debt-management policy as DEV-SPEC.md, ensuring consistency before implementation begins.

Core Features & Use Cases

  • Documents Code Standards: language conventions, naming, and security rules that teams must follow.
  • Establishes Commit Protocol and Review Criteria: standardizes commits and code reviews to maintain quality.
  • Defines Debt Management policy: outlines how technical debt is tracked and resolved.
  • Use Case: a new project can generate a definitive, shared development spec at project inception.

Quick Start

Invoke dev-discipline to produce .planning/DEV-SPEC.md containing Code Standards, Commit Protocol, Review Criteria, and Debt Management.

Frequently Asked Questions about dev-discipline

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

FAQPage Schema
How do I establish coding standards and a commit protocol before starting a software project?

To establish coding standards and a commit protocol before implementation, generate a DEV-SPEC.md file. This working agreement codifies code conventions, review criteria, and debt management policies into a single source of truth for the team.

What is the best way to document technical debt management policy for a development team?

Documenting technical debt management policy is done by creating a formal development specification. This specification outlines how technical debt is tracked and resolved, ensuring the team maintains a consistent approach to code quality throughout the project lifecycle.

How do I set up code review criteria for a new software project?

Setting up code review criteria involves defining standardized review rules within a project specification document. By establishing these criteria before code is written, teams ensure consistent quality control and alignment with security rules during implementation.

Can I use a single development spec to manage project standards, commits, and debt tracking?

Yes, a single development spec can manage project standards, commits, and debt tracking. Generating a DEV-SPEC.md file creates a unified working contract that codifies code standards, commit protocols, review criteria, and debt management policy together.

When do I need to create a development specification for my software project?

You need to create a development specification at the start of a software project, before any code is written. Establishing this working agreement early ensures all team members follow consistent development standards, workflows, and debt management practices.

Does the dev-discipline Skill generate the development spec automatically?

The dev-discipline Skill generates the development spec automatically by producing a DEV-SPEC.md file. It outputs this file to the .planning directory, containing structured sections for code standards, commit protocol, review criteria, and debt management.