plan

Create and move Markdown plan files across backlog, next, active, testing, and done stages.

2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/soliblue/cloude --skill plan-soliblue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/soliblue/cloude/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/soliblue/cloude --skill plan-soliblue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans solve the problem of disorganized work items by providing a simple, portable ticket-like system that moves through a lifecycle from backlog to done.

Core Features & Use Cases

  • Lightweight plan files stored in plans/ with a defined lifecycle (backlog, next, active, testing, done).
  • Clear progression rules and naming conventions to track work items, priorities, and status.
  • Use cases include creating new work items, promoting them as work progresses, and archiving completed plans for reference.

Quick Start

Create a new plan by adding a Markdown file in plans/backlog/ named using kebab-case-description.md, with YAML frontmatter including name and description. Move plans between stages using simple filesystem commands, for example: mv plans/backlog/my-feature.md plans/next/; mv plans/next/my-feature.md plans/active/; mv plans/active/my-feature.md plans/testing/; mv plans/testing/my-feature.md plans/done/.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I manage a project backlog using simple markdown files?

Manage a project backlog by creating markdown files in a plans/ directory, moving them through lifecycle stages like backlog, next, active, testing, and done using simple filesystem commands.

What is the best way to track feature work and bug fixes without a heavy project management tool?

Track work by creating ticket-like plan files with YAML frontmatter containing a name and description, then moving them between lifecycle folders to track status from backlog to done.

How do I move a ticket through an agile workflow using filesystem commands?

Move tickets through an agile workflow by executing filesystem commands like mv plans/backlog/my-feature.md plans/next/ to transition items between the required lifecycle stage directories.

Do I need a database to track work items and their lifecycle stages?

No database is needed to track work items. The system uses a portable file-based approach where each plan is a kebab-case markdown file stored inside specific lifecycle subfolders.

What file format and structure do plan tickets require?

Plan tickets require a markdown file named with kebab-case-description.md that includes YAML frontmatter with name and description fields, stored inside the plans/ directory structure.

How does a file-based ticketing system handle state transitions for project management?

A file-based ticketing system handles state transitions by explicitly moving markdown plan files between predefined stage directories, ensuring clear progression rules from backlog to done.