skills.rest
mckissinger
mckissingerCOMMUNITY
Explore all skills by this author →
GitHub

spec-feature

Define feature specifications with screens, interactions, and milestone criteria.

1|Updated Jun 29, 2026
Search Tags:#design system#verification#feature specification#autonomous development#milestone planning#software workflow
One-click install
npx skills add https://github.com/mckissinger/keel --skill spec-feature-mckissinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-feature
Source: https://github.com/mckissinger/keel/tree/main/skills/spec-feature
Command: npx skills add https://github.com/mckissinger/keel --skill spec-feature-mckissinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents feature development from starting with vague requirements by turning a single feature idea into a complete, build-ready specification with resolved decisions, designed screens, and verified milestones.

Core Features & Use Cases

  • Feature Interviewing: Systematically discovers screens, states, interactions, data requirements, edge cases, and integration seams before implementation begins.
  • Design Composition & Milestones: Creates feature screen references from an existing design system and defines milestones with logic, UX completeness, and fidelity requirements.
  • Use Case: Use this Skill when a product team needs to prepare one feature for a fresh autonomous build session while preserving product intent and verification standards.

Quick Start

Use the spec-feature skill to create a complete implementation plan for the next feature using the existing product foundation and design system.

Frequently Asked Questions about spec-feature

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

FAQPage Schema
How do I write a feature specification that is ready for autonomous development?▼

Feature specification for autonomous development requires resolving requirements, screens, interactions, and milestone criteria before implementation. You must conduct feature interviews to discover edge cases and map route ownership to produce a self-contained plan.

What is the best way to prevent vague requirements before starting feature implementation?▼

Preventing vague requirements involves systematically interviewing to discover data requirements, states, and integration seams. This process turns a single feature idea into a complete, build-ready specification with resolved decisions and verified milestones.

How do I create feature screen references from an existing design system?▼

Creating feature screen references from a design system involves composing existing components into planned layouts. This aligns visual design with interaction requirements before generating the final implementation plan.

Can I define milestone verification rules for individual software features?▼

Yes, you can define milestone verification rules for individual software features. This involves setting specific logic, UX completeness, and fidelity requirements to ensure the feature meets verification standards before the build session concludes.

Does feature specification work without a pre-existing design system composition?▼

Feature specification heavily relies on a pre-existing design system composition to create accurate screen references. Without it, resolving design alignment and ensuring build readiness for autonomous development becomes significantly more difficult.

How do I map route ownership when planning a new software feature?▼

Mapping route ownership involves assigning specific application routes to the new feature during the specification phase. This ensures integration seams are identified and the self-contained implementation plan covers all necessary navigation paths.

Related Skills

Explore More Software Engineering Skills→
djkloopdjkloop

shape

Conduct a structured discovery interview and produce a design brief.

Community
Intermediate
Huddo121Huddo121
1

feature-planner

Explore codebases and generate self-contained Cursor Plans for feature work.

Community
Advanced
mckissingermckissinger
1

spec-change

Plan small software changes into milestone specifications with verification methods.

Community
Advanced
SSiertsemaSSiertsema

example-mapping

Run example-mapping sessions to produce four-card outputs with ready-or-not verdicts.

Community
Intermediate