Browse / Productivity Workflow / Task Board Planning

Task Board Planning

Transforms user requests into comprehensive, well-researched implementation plans for software development tasks.

SkillProductivity WorkflowTask ManagementPlanningCode Search

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Rigorous 5-phase planning workflow (Understand, Research, Design, Document, Validate)
  • Leverages project-specific context (domain, stack, architecture) for tailored plans
  • In-depth codebase research and dependency analysis before planning
  • Generates detailed plan files using a standardized template and file naming convention
  • Strict plan-only constraint, focusing solely on documentation without code implementation

Use cases

  • Breaking down a complex user-requested feature into a phased implementation plan.
  • Creating a detailed technical plan for a significant code refactoring effort.
  • Documenting the findings and proposed approach from a technical exploration or research task.

FAQ

What does the Task Board Planning skill do?

It acts as a planning specialist, transforming software development requests into detailed, well-researched implementation plans. It focuses strictly on planning and documentation, not code implementation.

When should I use this skill?

Use it for planning complex features, significant refactors, or breaking down large epics. It's ideal for any task that requires technical design, research, and impact assessment before coding begins.

How does this skill improve my development workflow?

It introduces a structured, research-first approach to planning. By creating comprehensive plans upfront, it reduces ambiguity, identifies dependencies early, and ensures a clear, shared understanding of the technical approach.

What are its key capabilities?

It follows a rigorous 5-phase process (Understand, Research, Design, Document, Validate), performs in-depth codebase research, analyzes dependencies, and generates standardized plan files for your project's backlog.

Does this skill write any code?

No. This skill has a strict plan-only constraint. Its sole purpose is to create high-quality documentation and implementation plans, ensuring that planning is a distinct and thorough step before development.