plan-todo

Convert Linear backlog issues into structured test-driven implementation plans.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/lucaswall/food-scanner --skill plan-todo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-todo
Source: https://github.com/lucaswall/food-scanner/tree/main/.claude/skills/plan-todo
Command: npx skills add https://github.com/lucaswall/food-scanner --skill plan-todo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts Linear Backlog issues into structured, test-driven implementation plans at the project root, enabling teams to map work to actionable tasks.

Core Features & Use Cases

  • Plan by issue: Convert a single Linear issue (e.g., plan FOO-123) into a detailed PLANS.md outline.
  • Plan multiple items: Generate plans for all Backlog items or by specific criteria (labels, keywords) and move them to Todo.
  • CLAUDE.md alignment: Read CLAUDE.md to follow project conventions and MCP patterns.
  • Documentation generation: Produce a complete PLANS.md including prerequisites, tasks, and MCP usage.

Quick Start

Plan a specific issue using a natural language instruction, for example: "plan FOO-123". The planner will create PLANS.md and move the related issues to Todo in Linear.

Frequently Asked Questions about plan-todo

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

FAQPage Schema
How do I convert Linear backlog issues into a test-driven implementation plan?

You can convert Linear backlog issues into a structured PLANS.md file by instructing the planner with a natural language command like "plan FOO-123", which analyzes the codebase and writes a test-driven implementation plan at the repository root.

Can I generate PLANS.md for multiple Linear issues or filter by labels?

Yes, you can generate plans for all backlog items or filter by specific labels and keywords. After planning, the tool automatically moves the targeted Linear issues to the Todo state.

How does planning Linear issues align with existing project conventions?

The planner reads the CLAUDE.md file to follow existing project conventions and analyzes the codebase to identify patterns, ensuring the generated PLANS.md aligns with established development guidelines.

What is included in the PLANS.md file generated from Linear issues?

The generated PLANS.md includes comprehensive details on prerequisites, specific tasks, and MCP usage guidance, mapping Linear issues into actionable, test-driven implementation steps at the repository root.

Do I need a CLAUDE.md file to plan Linear issues at the repository root?

While not strictly required, having a CLAUDE.md file is recommended because the planner reads it to follow project conventions and MCP patterns when generating the PLANS.md file at the repository root.