specify

Generate order.md and todo.md specifications from feature requests.

5|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/kzytateishi/spikeee-plugins-marketplace --skill specify-kzytateishi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/kzytateishi/spikeee-plugins-marketplace/tree/main/plugins/dev-workflow/skills/specify
Command: npx skills add https://github.com/kzytateishi/spikeee-plugins-marketplace --skill specify-kzytateishi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate precise, implementation-ready specifications and task lists from a feature request, reducing back-and-forth and aligning teams before coding.

Core Features & Use Cases

  • Scenario detection and classification into New Feature, Improvement, Bugfix, Spike, or Chore, with corresponding templates and references.
  • Codebase analysis to tailor the spec to project conventions, architecture, and existing patterns.
  • Specification generation that outputs order.md and a task checklist that becomes todo.md.
  • Deterministic file outputs under a structured path (e.g., specs/{feature-name}/) for reproducible workflows and reviews.

Quick Start

Generate a specification for the given feature request to produce order.md and todo.md.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I generate implementation-ready specifications and task lists from feature requests?

To generate implementation-ready specifications and task lists, provide a feature request to trigger codebase analysis. The tool outputs structured order.md and todo.md files under specs/{feature-name}/, matching project conventions.

Can I create a todo.md checklist for different scenarios like bugfixes and chores?

Yes, you can create a todo.md checklist for bugfixes and chores. The tool detects scenarios like New Feature, Improvement, Bugfix, Spike, or Chore, applying corresponding templates and references to generate tailored task lists.

What is the best way to align teams on feature workflows before coding?

The best way to align teams on feature workflows is generating precise specs with concrete file paths and templates. Analyzing the codebase tailors the output to project architecture, reducing back-and-forth before implementation.

Does the specification generator analyze existing codebase patterns and conventions?

Yes, the specification generator analyzes existing codebase patterns and conventions. It inspects project architecture to tailor the generated order.md and todo.md documents, ensuring the output follows established project patterns.

Where are generated specification files stored for reproducible workflows?

Generated specification files are stored deterministically under a structured path like specs/{feature-name}/. This default placement ensures reproducible workflows and straightforward reviews for the order.md and todo.md outputs.