skills.rest
HeadyAI
HeadyAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

heady-feature-forge

Develop end-to-end feature specifications for Heady platform capabilities.

1|Updated Mar 24, 2026
Search Tags:#design#architecture#user-stories#acceptance-criteria#data-models#feature-spec#api-surface
One-click install
npx skills add https://github.com/HeadyAI/heady-context --skill heady-feature-forge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: heady-feature-forge
Source: https://github.com/HeadyAI/heady-context/tree/main/heady-skills/heady-feature-forge
Command: npx skills add https://github.com/HeadyAI/heady-context --skill heady-feature-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to convert vague feature ideas into concrete, shippable specifications that guide design, engineering, and QA.

Core Features & Use Cases

  • Structured templates for user stories, architecture sketches, API surfaces, data models, and acceptance criteria.
  • A repeatable process to scope, validate, and align stakeholders on feature feasibility and success metrics.

Quick Start

Create a complete feature spec by outlining user stories, architecture, API surface, data models, and acceptance criteria.

Frequently Asked Questions about heady-feature-forge

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

FAQPage Schema
How do I create end-to-end feature specifications for new platform capabilities?▼

Feature specifications are created by applying structured templates to outline user stories, architecture sketches, API surfaces, data models, and acceptance criteria for new platform capabilities. This process scopes, validates, and aligns stakeholders on feasibility and success metrics.

What is the best way to structure user stories and acceptance criteria for a feature spec?▼

Structuring user stories and acceptance criteria requires a repeatable process using predefined templates to ensure clear, testable outcomes. The spec format enforces clear acceptance criteria and guardrails to guide design, engineering, and QA teams effectively.

Can I generate architecture sketches and API surfaces for HeadyWeb or Latent OS features?▼

Yes, feature specs can be developed across HeadyWeb, HeadyBuddy, HeadyAI-IDE, or Latent OS. The specification process covers architecture sketches and API surfaces specifically tailored to these platform environments.

How do I convert vague feature ideas into shippable data models and feature specs?▼

Converting vague ideas into shippable specs involves applying a structured template to validate user stories, architecture, and data models. This ensures product teams produce concrete specifications with testable outcomes and clear guardrails.

Does the feature specification process include testable outcomes and guardrails?▼

Yes, the feature specification process ensures the document includes explicit guardrails and testable outcomes. It enforces a structured spec format with clear acceptance criteria to validate feature feasibility and alignment.

Related Skills

Explore More Product & Management Skills→
adrianliechtiadrianliechti
4

write-spec

Convert vague feature ideas into structured PRDs with goals and scope.

Community
Advanced
jschultejschulte
3

implement

Automates implementing missing features from finalized specifications via Speckit workflows.

Community
Intermediate
senior-sigansenior-sigan

design

Design system architectures and API specifications for scalable software.

Community
Advanced
xloxn69xloxn69
7

agileflow-story-writer

Convert feature descriptions into structured user stories with acceptance criteria.

Community
Intermediate