skills.rest
pandejesal
pandejesalCOMMUNITY
Explore all skills by this author →
GitHub

specify

Generates technology-agnostic feature specifications with requirements, scenarios, and clarification markers.

Updated Sep 14, 2026
Search Tags:#planning#specification#requirements#clarification#acceptance criteria#spec-driven development#feature spec
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill specify-pandejesal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/specify
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill specify-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a feature specification that stays free of implementation details while capturing testable requirements, measurable success criteria, and unresolved ambiguities is hard to do consistently, especially when existing specs or external SDD sources already exist in the repository. ## Core Features & Use Cases - Spec Generation: Produces .swarm/spec.md with numbered functional requirements (FR-###), success criteria (SC-###), Given/When/Then user scenarios, and edge cases, with no technology stack or implementation details. - Existing Spec Handling: Detects native, OpenSpec, and Spec-Kit sources via /swarm sdd status, then archives, refines, projects, or disambiguates them with explicit user consent. - Clarification Funnel: Classifies uncertainties, consults a critic sounding board, applies a 5-minute research budget, and emits [NEEDS CLARIFICATION] markers only for surviving items. - External Plan Import: Reverse-engineers a spec from a user-provided implementation plan and validates the plan against task format rules. - Use Case: A product owner asks to "specify a notification preferences feature"; the skill checks for existing specs, scans the codebase, consults SME research, and writes a complete spec with testable requirements. ## Quick Start Ask the assistant to specify a new feature, for example: "Write a spec for user notification preferences with acceptance criteria."

Frequently Asked Questions about specify

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

FAQPage Schema
How do I write a feature specification without implementation details?▼

Describe what users need and why, using numbered functional requirements with MUST/SHOULD language and measurable success criteria. Exclude technology stacks, file paths, API designs, and code structure so each requirement stays independently testable.

What happens when a spec already exists in the repository?▼

The protocol runs a status check to classify the existing spec as native or non-native. Native specs can be overwritten after archiving to a versioned file or refined via clarification; non-native OpenSpec or Spec-Kit sources require explicit user consent before projection.

Can I import an existing implementation plan into a spec?▼

Yes. Provide the plan as markdown or pasted text, and the protocol reverse-engineers functional requirements, success criteria, and user scenarios from it. It also validates task format rules such as file limits and explicit dependencies, reporting findings as suggestions only.

How are unresolved ambiguities handled during specification?▼

Uncertainties pass through a clarification funnel that classifies each item, consults a critic sounding board, and applies a 5-minute research budget. Only items surviving the funnel become [NEEDS CLARIFICATION] markers; resolved items are recorded as explicit assumptions.

What are the limitations of a technology-agnostic spec?▼

The spec deliberately excludes stack choices, schemas, and API designs, so it cannot guide implementation directly. Downstream planning modes must translate requirements into concrete tasks, and QA gate selection is deferred to the planning phase.

Related Skills

Explore More Product & Management Skills→
GregM1991GregM1991

to-spec

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

Community
Intermediate
leeoveryleeovery
27

technical-planning

Transform written specifications into structured software delivery plans with phases and tasks.

Community
Advanced
LerianStudioLerianStudio
205

pre-dev-research

Dispatch three parallel research agents to collect codebase patterns and framework documentation.

Official
Advanced
emergent-companyemergent-company
1

openspec-sync-specs

Synchronize delta specification files into main specification files using the openspec CLI.

Official
Advanced