spec-master

Organize specifications, plans, tasks, issues, ADRs, and change logs in a structured directory.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/timothyshen/word-game --skill spec-master
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-master
Source: https://github.com/timothyshen/word-game/tree/main/.claude/skills/spec-master
Command: npx skills add https://github.com/timothyshen/word-game --skill spec-master

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the documentation process for software development, ensuring that specifications, plans, and tasks are clearly defined and managed before and during implementation.

Core Features & Use Cases

  • Documentation-Driven Development: Enforces a workflow where documentation (specs, plans, tasks) precedes or guides code development.
  • Lifecycle Management: Manages the creation, updating, and closure of development phases, tasks, and issues.
  • Collaboration: Facilitates clear communication between documentation and code by linking spec-master with doc-keeper.
  • Use Case: When starting a new feature, use this Skill to create a spec_* file outlining requirements, break it down into task_* items, and then track implementation progress against these documents.

Quick Start

Use the spec-master skill to create a new task for the current phase.

Frequently Asked Questions about spec-master

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

FAQPage Schema
How do I manage specifications and tasks in a documentation-driven development workflow?

Documentation-driven development manages specifications, plans, and tasks by creating structured spec_* and task_* files before implementation. This ensures requirements are clearly defined and tracked throughout the development lifecycle.

What's the best way to track architectural decision records and change logs during software development?

Tracking architectural decision records and change logs involves organizing them within a structured directory. This approach enforces phase-based development cycles, ensuring decisions and changes are systematically recorded and resolved.

Can I synchronize software development specifications with code documentation?

Synchronizing specifications with code documentation is possible by integrating with a doc-keeper skill. This collaboration links defined plans and tasks directly to code, maintaining alignment between documentation and implementation.

How do I create and track development phases and issues for a new feature?

Creating and tracking development phases involves defining requirements in a spec_* file, breaking them into task_* items, and managing issue resolution against these documents. This lifecycle management tracks progress from phase creation to closure.

Does documentation-driven development support agile commit conventions and task tracking?

Yes, documentation-driven development supports agile workflows by enforcing phase-based cycles, tracking tasks, and adhering to commit conventions. It organizes specifications and plans to guide implementation and progress tracking.