skills.rest
andrewcodesit
andrewcodesitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

define-spec

Creates concise implementation-ready specs from project ideas, feature requests, or vague goals.

Updated May 13, 2026
Search Tags:#requirements#project planning#acceptance criteria#feature specification#spec#scope definition
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill define-spec-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define-spec
Source: https://github.com/andrewcodesit/skills/tree/main/skills/project-management/define-spec
Command: npx skills add https://github.com/andrewcodesit/skills --skill define-spec-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague project ideas and feature requests often lead to misaligned implementations because no clear spec exists before work begins. This Skill turns loose goals into a concise, decision-oriented spec with defined scope, requirements, and acceptance criteria. ## Core Features & Use Cases - Context-Aware Questioning: Reads AGENTS.md, context files, README, and linked tickets before asking only for missing product decisions. - Standardized Spec Format: Produces a structured Markdown spec covering goal, stakeholders, scope, requirements, acceptance criteria, and open questions. - Organized Storage: Saves specs to ~/.agents/specs/<repo>/ with date-stamped filenames, or repo-local when requested. - Use Case: You have a rough feature idea like "add team invitations". The Skill reads your repo context, asks a few concrete questions, and saves a spec with observable requirements and testable acceptance criteria ready for task breakdown. ## Quick Start Ask the agent to create a spec for your feature idea, for example: "Write a spec for adding team invitation support to the app."

Frequently Asked Questions about define-spec

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

FAQPage Schema
How do I turn a feature idea into a spec?▼

Describe your idea or feature request and ask for a spec. The Skill reads your repo context files first, asks only concrete questions about missing product decisions, then saves a structured Markdown spec with scope, requirements, and acceptance criteria.

What should a good feature spec include?▼

A good spec includes the goal, stakeholders, scope, explicit out-of-scope items, observable requirements, testable acceptance criteria, and open questions. This Skill uses exactly that format, keeping sections concise and omitting any that do not apply.

Where are the generated spec files saved?▼

Specs are saved to ~/.agents/specs/<repo>/ with a date-stamped filename like YYYY-MM-DD-<slug>.md. If you explicitly request repo-local documentation, the spec is saved inside the repository instead.

Does the spec include implementation plans or tasks?▼

No. The spec captures observable behavior and requirements only, not implementation plans. Task creation is intentionally deferred to a separate breakdown-tasks step after the spec is accepted.

When should I not write a spec for a change?▼

Skip the spec for trivial changes with no product or behavior decisions, such as typo fixes or dependency bumps. Specs add value when scope, requirements, or acceptance criteria are ambiguous and need alignment before implementation.

Related Skills

Explore More Product & Management Skills→
AO-HySAO-HyS

to-spec

Synthesizes conversation context into a structured spec published to the project issue tracker.

Official
Intermediate
dreamingechoesdreamingechoes
2

planning-and-task-breakdown

Break feature specs into verifiable tasks with acceptance criteria and dependencies.

Community
Advanced
ddobrinddobrin
8

spec-validator

Identify ambiguity, missing requirements, contradictions, and untestable criteria in software specifications.

Community
Advanced
HexSleevesHexSleeves

staff-brainstorming

Guide structured brainstorming from vague ideas to validated design specs.

Community
Advanced