start-dev

Update task statuses to IN PROGRESS across MASTER_PLAN.md by ID with validation checks.

Updated Nov 29, 2025
One-click install
npx skills add https://github.com/endlessblink/flow-state --skill start-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-dev
Source: https://github.com/endlessblink/flow-state/tree/main/.claude/skills/start-dev
Command: npx skills add https://github.com/endlessblink/flow-state --skill start-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces manual updates by automatically switching a task's status to IN PROGRESS in the central MASTER_PLAN.md, ensuring consistency across Roadmap, Details, and Subtasks.

Core Features & Use Cases

  • Automatic Progress Update: Updates all three locations in MASTER_PLAN.md to reflect IN PROGRESS.
  • ID-based Activation: Accepts IDs like TASK-123 or BUG-456 and normalizes them for reliable updates.
  • Safeguards & Validation: Verifies task existence before updates and handles cases where tasks are already DONE or in-progress to avoid regressions.

Quick Start

Type start-dev TASK-123 to begin work on a task, which updates MASTER_PLAN.md accordingly.

Frequently Asked Questions about start-dev

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

FAQPage Schema
How do I update task status to IN PROGRESS in MASTER_PLAN.md?

You can update task status to IN PROGRESS in MASTER_PLAN.md by passing a task ID like TASK-123. The workflow automatically synchronizes the status across the roadmap table, detailed section header, and related subtasks.

What happens if I try to update a task that is already marked DONE?

The validation workflow prevents updating tasks that are already DONE or in an incompatible state. It enforces safeguards to avoid regressions by verifying task existence and checking status compatibility before applying any updates.

Can I use custom task IDs like BUG-456 for task tracking in MASTER_PLAN.md?

Yes, task tracking accepts ID-based activation using formats like BUG-456 or TASK-123. The system normalizes these IDs to ensure reliable and consistent updates across all three locations in the MASTER_PLAN.md document.

Does updating task status preserve the existing formatting in MASTER_PLAN.md?

Yes, the status update process explicitly preserves formatting while applying changes. It normalizes task IDs and modifies the roadmap table, section headers, and subtasks without disrupting the original document structure.

What is the best way to maintain consistency across the roadmap and subtasks when starting development?

To maintain consistency when starting development, use an automated workflow to switch task status. It updates all three locations in MASTER_PLAN.md simultaneously, ensuring the roadmap, details, and subtasks reflect IN PROGRESS.

Do I need to manually locate all task references in MASTER_PLAN.md before starting work?

No, manual updates are unnecessary. The workflow automatically locates and updates the roadmap table, detailed section header, and any related subtasks in MASTER_PLAN.md based on the provided task ID, reducing manual overhead.