spec-feature

Create a structured feature specification and implementation plan from a feature request.

1|Updated Mar 3, 2026

Search Tags:#implementation planning #feature specification #work breakdown #docs generation #architecture recall #Hindsight MCP #git ticketing

Ready to run

npx skills add https://github.com/AndreJorgeLopes/devflow --skill spec-feature-andrejorgelopes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-feature
Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/spec-feature
Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill spec-feature-andrejorgelopes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It forces a consistent, architecture-aware planning workflow so you don’t start coding without alignment, reused knowledge, or a clear implementation path.

Core Features & Use Cases

Ticket-aware spec kickoff: Detects a ticket ID from your current git branch and uses it to label the chapter context.
Architecture recall and codebase mapping: Uses Hindsight recall to retrieve prior architectural decisions and constraints, then identifies what parts of the system are impacted.
Spec + task checklist output: Writes a structured spec into docs/specs/<feature-name>.md, breaks the plan into session-completable tasks, and retains decisions for future sessions.

Quick Start

Ask your AI to run the spec-feature skill with a clear description of the feature you want to build and its constraints.

Frequently Asked Questions about spec-feature

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

FAQPage Schema

How do I generate a feature specification and implementation plan from a feature request?▼

To generate a feature specification, provide a clear feature description and constraints to trigger architecture recall, domain impact analysis, and task breakdown, resulting in a deterministic spec file and a session-completable checklist.

How does git branch ticket detection work for feature planning?▼

Git branch ticket detection automatically extracts a ticket ID from your current branch name and uses it to label the chapter context, ensuring the feature specification and implementation plan are tracked against the correct issue.

What is the best way to map architecture impact before writing code?▼

The best way to map architecture impact is using Hindsight recall to retrieve prior architectural decisions and constraints, then identifying domain, application, and infrastructure components affected by the new feature request.

Can I use Hindsight recall to retrieve prior architectural decisions for new features?▼

Yes, Hindsight recall retrieves prior architectural decisions and constraints during feature specification, ensuring the implementation plan reflects past choices and retains new decisions for future session continuity.

Does spec generation automatically start writing code after creating the task breakdown?▼

No, feature spec generation enforces a controlled handoff to the planning phase without auto-starting implementation, ensuring alignment on the structured spec and task checklist before any code is written.

Where are generated feature specification files stored?▼

Generated feature specification files are stored deterministically in the docs/specs/ directory using the feature name, creating a structured markdown document for architecture-aware planning and implementation tracking.