to-features

Generate user-facing features from CONTEXT.md and ADRs into FEATURES.md.

3|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/soulmachine/skills --skill to-features
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-features
Source: https://github.com/soulmachine/skills/tree/main/to-features
Command: npx skills add https://github.com/soulmachine/skills --skill to-features

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, markdown, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates the translation of domain understanding into user-facing features, bridging the gap between conceptual knowledge and actionable requirements.

Core Features & Use Cases

  • Feature Enumeration: Generates a comprehensive list of user-facing features derived from CONTEXT.md and ADRs.
  • Version Control Integration: Ensures feature tracking aligns with the project's version control system.
  • Collaboration: Supports collaborative review and refinement of feature lists.

Quick Start

Run the to-features skill after /grill-with-docs to generate FEATURES.md at the repo root, and before /to-prd to refine feature specifications.

Frequently Asked Questions about to-features

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

FAQPage Schema
How do I generate user-facing features from domain context documents?

To generate user-facing features from domain context, you process context documents and architectural decisions to enumerate actionable product features. This bridges domain understanding and product specification by producing a comprehensive feature list derived directly from your project's contextual knowledge.

What is the best way to transition domain understanding into product specifications?

Transitioning domain understanding into product specifications involves translating conceptual knowledge into actionable feature requirements. By processing domain context and architectural decisions, you create a structured feature list that bridges the gap between high-level domain concepts and concrete product specifications.

How do I create a comprehensive feature list from ADRs and context documents?

Creating a feature list from ADRs and context documents requires analyzing architectural decisions alongside domain context. This process extracts user-facing features and generates a comprehensive feature documentation file, supporting collaborative review and version control alignment for feature tracking.

Can I use markdown for product feature documentation and version control integration?

Yes, markdown is supported for product feature documentation, enabling version control integration for feature tracking. The process generates a markdown file at the repository root, ensuring feature documentation aligns with the project's version control system for collaborative review and refinement.

Do I need Python to enumerate product features from architectural decisions?

Yes, Python is a required dependency to enumerate product features from architectural decisions. The feature enumeration process relies on Python scripts to process context documents and generate the feature documentation that bridges domain understanding with product specifications.

When should I generate feature specifications during product development?

Feature specifications should be generated after establishing domain understanding through context documents and before refining detailed product requirements. This intermediate step ensures architectural decisions are translated into actionable user-facing features prior to creating comprehensive product requirement documents.