flowai-spec

Decompose large features into dependency-ordered phases and actionable tasks.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/korchasa/foxcode --skill flowai-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowai-spec
Source: https://github.com/korchasa/foxcode/tree/main/.claude/skills/flowai-spec
Command: npx skills add https://github.com/korchasa/foxcode --skill flowai-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating comprehensive, phased specifications for large software features, enabling teams to plan, track, and execute multi-session work with clear boundaries and dependencies.

Core Features & Use Cases

  • Produces a dedicated spec document at documents/spec-{name}.md that records dependency-ordered phases, atomic tasks, and per-phase status.
  • Enforces explicit phase boundaries and prerequisites to prevent scope creep and miscommunication.
  • Supports collaboration across product, design, and engineering by providing a single source of truth for complex features.
  • Use Case: When a feature spans multiple files and teams, generate a per-phase plan that can be reviewed and updated iteratively.

Quick Start

Run flowai-spec to generate documents/spec-{name}.md for your feature.

Frequently Asked Questions about flowai-spec

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

FAQPage Schema
How do I plan large features that span multiple files and sessions?

Planning large features involves decomposing work into dependency-ordered phases and atomic tasks with defined boundaries. This produces a single source of truth for cross-functional teams to iteratively track and execute complex multi-session work.

How do I create phased specifications for complex software features?

Creating phased specifications involves generating a dedicated spec document that records prerequisite phases, atomic tasks, and per-phase status. This enforces explicit boundaries and prerequisites to prevent scope creep during cross-functional team collaboration.

What is the best way to track per-phase status for multi-session feature development?

Tracking per-phase status is done by maintaining a structured spec document with dependency-ordered phase definitions and defined done criteria. This enables iterative updates and provides clear status management across multiple work sessions.

Can I use a chat-first workflow to generate specification documents without writing code?

Yes, you can use a no-code, chat-first workflow to generate specification documents. This approach produces structured phase definitions and tracks per-phase status without requiring additional code components or dependencies.

When do I need explicit phase boundaries and prerequisites for feature planning?

You need explicit phase boundaries and prerequisites when a feature spans multiple files and cross-functional teams. This structure prevents scope creep and miscommunication by enforcing dependency-ordered phases with clear done criteria.