spec

Draft and manage feature specifications across Drafts, Active, and Done lifecycle folders.

10|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/istota-project/istota --skill spec-istota-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/istota-project/istota/tree/main/src/istota/skills/spec
Command: npx skills add https://github.com/istota-project/istota --skill spec-istota-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage specs for spec-driven development. Specs live in the user's notes_folder under Specs/ with three lifecycle subfolders — Drafts, Active, Done.

Core Features & Use Cases

  • Centralize and standardize the creation, review, and tracking of every feature spec.
  • Enforce a lifecycle from Drafts to Active to Done to ensure clarity, accountability, and traceability.
  • Support cross-project specs and operations like drafting, starting implementation, listing, showing, and editing specs.

Quick Start

Draft a new spec by providing a title and using the skill to organize it into Drafts, Active, and Done.

Frequently Asked Questions about spec

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

FAQPage Schema
What is spec-driven development and how do I manage feature specifications?

Spec-driven development manages feature specifications in a notes folder using a persistent lifecycle workflow with Drafts, Active, and Done subfolders to guide drafting, review, and implementation tracking.

How do I draft a new specification for a project feature?

Draft a new specification by providing a title, which the system organizes into a structured design doc within the Drafts subfolder, applying standardized frontmatter and content layout for tracking progress.

Can I track the lifecycle stages of active project specifications?

Yes, lifecycle stages are tracked explicitly by moving specifications between Drafts, Active, and Done subfolders, ensuring clarity, accountability, and traceability from initial design to implementation.

Does this specification management workflow support cross-project operations?

Yes, cross-project specification operations are supported, allowing users to list, show, and edit design documents across different scopes while maintaining a consistent folder structure and frontmatter.

What's the best way to organize design docs for implementation review?

Organize design docs using a structured frontmatter and content layout within a notes folder, separating them into Drafts for review, Active for implementation, and Done for completion tracking.