spec-and-plan

Name: spec-and-plan
Availability: InStock
Author: Endaoment

Convert free-form feature descriptions into technical specs and tracking issues.

Updated Feb 10, 2026

Search Tags:#planning #architecture #specification #issue-tracking #product-management #feature-design

Ready to run

npx skills add https://github.com/endaoment/fellowship-code --skill spec-and-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-and-plan
Source: https://github.com/endaoment/fellowship-code/tree/main/skills/spec-and-plan
Command: npx skills add https://github.com/endaoment/fellowship-code --skill spec-and-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning a free-form feature idea into a formally documented technical spec and actionable tracking issues.

Core Features & Use Cases

Transforms vague ideas into a structured spec stored under specs/{feature}/
Generates 3-15 actionable issues linked to the spec
Enables PMs and engineers to review before implementation

Quick Start

Describe a feature you want in free form and let the system generate a technical spec and 3-15 tracking issues ready for implementation.

Frequently Asked Questions about spec-and-plan

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

FAQPage Schema

How do I convert a free-form feature idea into a technical spec and tracking issues?▼

To convert a free-form feature idea into a technical spec and tracking issues, describe the feature in free form. The system generates a structured spec under specs/{feature}/ and creates 3-15 linked tracking issues for PMs and engineers.

What is the process for generating actionable issues from a feature description?▼

Generating actionable issues from a feature description requires a formal technical spec to exist first. The system enforces this spec-first workflow, following existing formats, and then produces 3-15 linked tracking issues ready for review.

When do I need a formal technical spec before creating tracking issues?▼

You need a formal technical spec before creating tracking issues during early-stage product development. This ensures PMs and engineers review a concrete specification before implementation, converting vague ideas into structured documentation and actionable tasks.

Can I generate a product specification without writing structured documentation manually?▼

Yes, you can generate a product specification without manual structuring by inputting a free-form feature description. The system automates turning the text into a formally documented technical spec stored in a dedicated feature directory.

Does issue tracking require a reviewed spec before implementation begins?▼

Yes, issue tracking requires a reviewed spec before implementation begins. The workflow mandates that PMs and engineers review the formal technical specification before moving forward with the generated actionable tracking issues.