flow-spec

Generate structured specifications with dependency-ordered phases and atomic tasks.

3|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/korchasa/flowai --skill flow-spec-korchasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-spec
Source: https://github.com/korchasa/flowai/tree/main/framework/skills/flow-spec
Command: npx skills add https://github.com/korchasa/flowai --skill flow-spec-korchasa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the complexity of large features by breaking them down into manageable, dependency-ordered phases, ensuring a clear roadmap and trackable progress.

Core Features & Use Cases

  • Phased Decomposition: Breaks down large features into distinct, logical phases.
  • Dependency Management: Clearly defines prerequisites for each phase.
  • Atomic Task Definition: Lists specific, actionable tasks within each phase.
  • Status Tracking: Enables tracking of phase completion from 'not-started' to 'done'.
  • Use Case: When planning a major new module for your application that involves multiple components and will take several development sprints, flow-spec can help you define the overall structure, identify dependencies between different parts, and create a clear plan for implementation.

Quick Start

Use the flow-spec skill to create a specification for the new user authentication system.

Frequently Asked Questions about flow-spec

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

FAQPage Schema
How do I break down large software features into manageable phases?

Phased decomposition breaks large software features into dependency-ordered phases and atomic tasks. This structured specification process analyzes prompts, codebase, and documentation to create a clear roadmap for complex development projects.

What is the best way to plan a multi-sprint project module with dependencies?

Planning a multi-sprint project module requires phased decomposition to define overall structure and identify dependencies. Generating a structured specification with atomic tasks ensures trackable progress from 'not-started' to 'done' across sprints.

When do I need detailed specification drafting for software architecture?

Detailed specification drafting for software architecture is needed when planning major new modules involving multiple components. It addresses the complexity of large features by ensuring a clear roadmap and defining prerequisites for each logical development phase.

Can I track task management status for individual phases during feature decomposition?

Yes, task management status tracking is enabled for individual phases during feature decomposition. The specification defines actionable atomic tasks within each phase and allows tracking completion status from 'not-started' to 'done'.

Do I need a Principal Software Architect role to generate project specifications?

Yes, generating project specifications requires a Principal Software Architect role to analyze prompts, codebase, and documentation. This role ensures comprehensive specification drafting for complex software development projects using dependency-ordered phases.