recursive-spec

Draft repo-aware 00-requirements.md with R# entries and acceptance criteria.

128|10|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/try-works/recursive-mode --skill recursive-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recursive-spec
Source: https://github.com/try-works/recursive-mode/tree/main/skills/recursive-spec
Command: npx skills add https://github.com/try-works/recursive-mode --skill recursive-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Co-author repo-aware 00-requirements.md for a new recursive-mode run, enabling planning and alignment before implementation and ensuring drafts stay out of the repo until approval.

Core Features & Use Cases

  • Repo-aware drafting of 00-requirements.md for new runs.
  • Interacts with repository docs, decisions, and memory to shape clear, testable requirements.
  • Supports an approval workflow that keeps drafts outside the repo until user consent to proceed.

Quick Start

Draft a repo-aware 00-requirements.md for a new recursive-mode run and seek user approval before writing the file.

Frequently Asked Questions about recursive-spec

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

FAQPage Schema
How do I draft repo-aware requirements for a new development run?

Draft repo-aware requirements by integrating repository docs, decisions, and memory to shape clear, testable R# entries for a new run. This creates a structured 00-requirements.md file with acceptance criteria before implementation begins.

Can I keep requirement drafts outside the repository until approved?

Yes, requirement drafts stay outside the repository until explicit user consent is granted. The approval workflow ensures planning and alignment happen before any file is written to the repository.

What is a repo-aware spec for a recursive-mode run?

A repo-aware spec for a recursive-mode run is a structured requirements document that scopes and integrates existing repository context and prior decisions. It outputs an 00-requirements.md file containing R# entries and run-creation guidance.

How do I create testable acceptance criteria for new run requirements?

Create testable acceptance criteria by interacting with repository docs and memory to shape clear requirements. The process drafts a structured 00-requirements.md file with R# entries and run-creation guidance for user approval.

Does the requirements drafting process work with existing repository decisions?

Yes, the requirements drafting process interacts directly with existing repository decisions, docs, and memory to shape clear requirements. It integrates this prior context to produce a structured 00-requirements.md file for the new run.

When do I need to use a structured requirements file for planning?

Use a structured requirements file when planning and aligning on a new recursive-mode run before implementation. It enables collaboration by drafting repo-aware 00-requirements.md with R# entries and acceptance criteria.