specops

Create and review YAML-based specs and plans for spec-driven development.

Updated Mar 11, 2025

Search Tags:#workflow management #spec-driven development #specops #codebase organization #plan protocol

Ready to run

npx skills add https://github.com/CodeForPhilly/codeforphilly-ng --skill specops-codeforphilly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specops
Source: https://github.com/CodeForPhilly/codeforphilly-ng/tree/main/.agents/skills/specops
Command: npx skills add https://github.com/CodeForPhilly/codeforphilly-ng --skill specops-codeforphilly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of spec-driven development by providing a comprehensive set of tools and protocols for defining, reviewing, and implementing code based on specifications.

Core Features & Use Cases

Spec Creation and Review: Facilitates the creation, review, and acceptance of specifications that define the desired state of the codebase.
Plan Protocol: Offers a structured approach to planning and tracking the implementation of specifications, enabling teams to manage workflows efficiently.
Spec-Driven Development Workflow: Integrates spec-first development practices into the codebase, ensuring that code implementation closely aligns with specifications.

Quick Start

To start using specops, create a new spec in the 'specs/' directory, review and accept it, then create a corresponding plan in the 'plans/' directory to guide the implementation.

Frequently Asked Questions about specops

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

FAQPage Schema

What is spec-driven development and how does a plan protocol help manage codebase workflows?▼

Spec-driven development defines the desired codebase state through specifications, and a plan protocol structures the implementation tracking. This ensures code implementation closely aligns with initial specifications and manages development workflows efficiently.

How do I start a spec-driven workflow using Markdown files and YAML frontmatter?▼

To start spec-driven development, create a specification using Markdown files with YAML frontmatter in the 'specs/' directory, review and accept it, then generate a corresponding implementation plan in the 'plans/' directory to guide coding.

Does spec-driven development require a specific codebase organization?▼

Yes, spec-driven development with this plan protocol requires a codebase explicitly organized with 'specs/', 'plans/', and 'references/' directories to properly store specification files, implementation plans, and protocol guidelines.

How does spec validation work during the spec review process?▼

Spec validation works by implementing specific protocols for spec review and plan creation, verifying that the Markdown specifications and their YAML frontmatter accurately define the desired state before code implementation begins.

What is the best way to manage team workflows for spec-first development?▼

The best way to manage spec-first workflows is adopting a structured plan protocol that tracks specification implementation from creation through review, ensuring team development decisions closely align with accepted specifications.

Why do I need to separate specifications and plans into different directories?▼

Separating specifications and plans into distinct 'specs/' and 'plans/' directories enforces a clear distinction between defining the desired codebase state and tracking the structured implementation steps required to achieve it.