spec

Create and maintain a living project specification in docs/SPEC.md.

1|Updated Apr 17, 2026

Search Tags:#design #planning #architecture #specification #sync #docs #brainstorm

Ready to run

npx skills add https://github.com/justincordova/agents --skill spec-justincordova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/justincordova/agents/tree/main/skills/spec
Command: npx skills add https://github.com/justincordova/agents --skill spec-justincordova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create and maintain a living project specification (docs/SPEC.md) that evolves with design decisions.

Core Features & Use Cases

Initial spec draft: Create the base SPEC.md with vision, goals, and architecture sections.
Sync and merge: Merge implemented design docs into SPEC.md using sync-docs.
Direct edits & mode switching: Update SPEC.md directly or initialize a greenfield spec via brainstorm.

Quick Start

Start by drafting your project name and vision, then create docs/SPEC.md with a complete SPEC structure.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I create a living project specification for a greenfield architecture?▼

Maintain project specifications by directly editing the SPEC.md document or using sync workflows to merge implemented design docs, ensuring your architecture documentation evolves with development decisions.

How does brainstorming help define initial project design and specifications?▼

Sync design docs into a project specification using the sync-docs workflow, which merges implemented design decisions and architectural updates directly into the living SPEC.md file.

What sections should be included in a structured software architecture specification?▼

This specification approach fits both greenfield projects needing initial design brainstorming and evolving development workflows requiring synchronization of design docs into a central SPEC.md file.

When should I use a single living spec document over multiple scattered design docs?▼

Use a single living spec document when you need to synchronize scattered design docs and architectural decisions into one structured file, preventing fragmented project planning and outdated documentation.