dev-planner

Parse frontend planning docs and generate a structured tasks.json.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill dev-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-planner
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/dev-planner
Command: npx skills add https://github.com/rachel353/fullty-plan --skill dev-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Frontend teams often struggle to translate design notes and requirements into concrete tasks and a runnable plan. This skill reads planning docs and UI scope to produce a coherent task graph and an initial tasks.json.

Core Features & Use Cases

  • Read planning docs (PRD/SRS, IA, conceptual models) and map them to frontend features and tasks.
  • Auto-generate tasks and organize them into tasks.json for the task-management workflow.
  • Support MVP scoping, dependencies, and design-validation flags to guide frontend development.

Quick Start

Plan the frontend work and generate tasks based on the planning docs.

Frequently Asked Questions about dev-planner

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

FAQPage Schema
How do I generate a tasks.json from frontend planning docs?

To generate a tasks.json from frontend planning docs, parse PRD/SRS and conceptual models to map UI scope into a structured task graph. This process organizes MVP dependencies and assigns design_validation_required flags for task-management workflows.

What is the best way to break down React UI components into development tasks?

The best way to break down React UI components into development tasks is parsing project planning docs and UI scope to produce a coherent component breakdown. This creates a structured task graph aligned with frontend feature planning and MVP scoping.

Can I use this to plan backend API development tasks?

No, you cannot use this to plan backend API development tasks. The frontend planning process specifically excludes backend and API work, focusing entirely on UI components, design validation, and frontend feature breakdowns.

How do I manage dependencies when planning an MVP frontend project?

Manage MVP frontend project dependencies by parsing planning docs to map UI scope into a structured tasks.json. This enforces schema compliance and aligns task dependencies within the task-management workflow.

When do I need to add a design_validation_required flag to a frontend task?

Add a design_validation_required flag to a frontend task when parsing UI scope and conceptual models indicates a component needs design review. This ensures design notes are actively tracked in the generated tasks.json.

Does this task generation process require external project management tools?

No, task generation does not require external project management tools. It parses internal planning docs and directly outputs a structured tasks.json file, enforcing schema compliance for your existing task-management workflow.