blade-plan

Automates planning and progressive execution of mid-scale development tasks involving 5-15 file changes.

277|68|Updated Nov 19, 2019
One-click install
npx skills add https://github.com/chillzhuang/Saber --skill blade-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blade-plan
Source: https://github.com/chillzhuang/Saber/tree/main/.claude/skills/blade-plan
Command: npx skills add https://github.com/chillzhuang/Saber --skill blade-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blade Plan provides a lightweight workflow to help teams analyze, plan, and execute mid-scale development tasks with structured steps, reducing ambiguity and back-and-forth.

Core Features & Use Cases

  • Structured planning for tasks involving 5–15 file changes across modules (e.g., adding a new feature, refactoring, or Starter integration).
  • Progressive task execution with built-in task tracking and optional auto mode.
  • Clear boundaries and recommended usage patterns to avoid scope creep and ensure reproducible results.

Quick Start

Start Blade Plan by describing a mid-scale development task to trigger the planning workflow.

Frequently Asked Questions about blade-plan

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

FAQPage Schema
How do I plan a multi-file development task across different modules?

To plan a multi-file development task, you can use a structured workflow that breaks work into progressive steps, tracking each file change to reduce ambiguity and ensure reproducible results.

What is the best way to execute a refactoring task involving 5 to 15 files?

Executing a refactoring task involving 5 to 15 files requires a disciplined workflow with structured analysis, task creation, and progressive execution to enforce clear boundaries and avoid scope creep.

Can I automate task execution for mid-scale development work?

Yes, you can automate task execution for mid-scale development work using an optional auto mode that handles progressive execution while enforcing build validation and avoiding modifications beyond the planned scope.

Does structured workflow planning work for adding a new feature across modules?

Structured workflow planning works for adding a new feature across modules by applying task tracking and progressive execution to manage the 5 to 15 file changes typically required.

When should I not use a structured task execution workflow?

You should not use a structured task execution workflow for changes outside the 5 to 15 file range or when modifications extend beyond the planned scope, as it enforces strict boundaries to prevent scope creep.