f2s-req-plan

Plans and implements coding tasks from requirement documents with tracked task checklists.

48|6|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-req-plan-double-coding-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: f2s-req-plan
Source: https://github.com/double-coding-lab/Flow2Spec/tree/main/.cursor/skills/f2s-req-plan
Command: npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-req-plan-double-coding-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a requirement or technical design document into implemented code often loses track of progress across sessions, leaving agents to rediscover task state. This Skill converts requirements into a persisted, resumable task plan under .task/ and drives implementation step by step. ## Core Features & Use Cases - Requirement-to-Task Planning: Parses technical design docs, requirement descriptions, or change requests into a snake_case task with a checklist (task.md), context file (context.md), and user to-dos (user-todos.md). - Resumable Task Lifecycle: Matches incoming requests against todo.json keywords to resume interrupted tasks, enforces checkbox discipline, and archives completed work to .task/completed/<YYYYMMDD>-<task-name>/. - Sub-Agent Orchestration: Optionally splits read-only parsing and business-code implementation across sub agents while the main agent exclusively owns todo.json writes and checkbox updates. - Use Case: Paste a feature change description, and the agent drafts the implementation checklist, persists it to .task/active/, implements each step, checks items off on disk, and archives the task when the archive gate passes. ## Quick Start Ask the agent to create a task plan from your requirement description and implement it step by step using f2s-req-plan.

Frequently Asked Questions about f2s-req-plan

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

FAQPage Schema
How do I turn a requirement document into an implementation task list?▼

Provide the technical design doc path or a free-text requirement description. The skill parses goals, scope, and affected files, then writes a checklist to task.md, context to context.md, and a todo.json entry under .task/active/ in the same turn.

How do I resume an interrupted coding task in a new session?▼

The skill matches your new input against keywords in .task/todo.json. On a match it reloads task.md, context.md, and user-todos.md, shows remaining checklist items, and continues from the first unchecked step without creating duplicate task folders.

Can sub agents implement parts of the task in parallel?▼

Yes, when subAgent is enabled in flow2spec.config.json. Sub agents handle read-only parsing and business code changes, but only the main agent may write todo.json, check off task.md steps, and merge user-todos.md updates.

When is a task allowed to be archived as completed?▼

Archiving requires every delivery-related step in task.md to be checked off, with cancelled items explained in the notes section. Only then is the folder moved to .task/completed/<YYYYMMDD>-<task-name>/ and its todo.json entry removed.

Does this skill depend on changeTracking configuration?▼

No. It operates independently of changeTracking.feat/fix/implement settings and always creates and maintains a task checklist, unless it is resuming an existing active task found via todo.json.