feature-flow

Structures feature ideas into implementable specifications with user stories, research, and success criteria.

6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kok1eee/o-m-cc --skill feature-flow-kok1eee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-flow
Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/feature-flow
Command: npx skills add https://github.com/kok1eee/o-m-cc --skill feature-flow-kok1eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams convert vague feature ideas into a structured, implementable specification so work can be planned, handed off, and implemented with fewer misunderstandings and rework.

Core Features & Use Cases

  • Guided interactive user-story elicitation (WHO / WHEN / GOAL) to avoid premature agreement and surface true needs.
  • Parallel prior-art research (market, OSS, UI patterns) or in-repo exploration for existing codebases, plus data/operation mapping and observable success criteria.
  • Automated spec generation with a Reader Test loop and an output markdown plan ready for discovery-council, design, or direct implementation; ideal for product planning, feature additions, and prototyping.

Quick Start

Run the feature-flow skill with a concise feature description, for example: /o-m-cc:feature-flow "Add user profile picture upload" --existing.

Frequently Asked Questions about feature-flow

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

FAQPage Schema
How do I turn a vague feature idea into an implementable user story spec?

To turn a vague idea into a user story spec, use guided interactive elicitation to define the WHO, WHEN, and GOAL. This prevents premature agreement and surfaces true needs before generating implementation plans.

Can I generate a feature specification for an existing web application codebase?

Yes, you can generate a feature specification for an existing web application by inspecting the filesystem to detect modes and exploring in-repo prior art to map data and operations accurately.

How does multi-agent research integrate into feature planning?

Multi-agent research integrates into feature planning by spawning parallel agents for market and UI pattern exploration, then consolidating their outputs into a single, handoff-ready spec document.

What is the best way to ensure my feature spec is ready for design and implementation handoff?

The best way to ensure handoff readiness is applying a Reader Test loop to the generated markdown plan. This verifies that success criteria and operational mappings are clearly understood by downstream teams.

Does feature-flow require interactive clarification before generating the final plan file?

Yes, feature-flow requires interactive clarification during the elicitation phase. This ensures all ambiguities are resolved before the automated spec generation and markdown plan file output.