quick-plan

Generate concise backlog planning documents from user input.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables quick capture of ideas by generating concise backlog plan documents that follow a standard template, reducing context loss and speeding up planning.

Core Features & Use Cases

  • Lightweight planning: Generate starter backlog plans from brief inputs.
  • Template-driven: Writes plans using the standard backlog template to backlog/plans/.
  • Quick-start ready: Produces date-based filenames for easy organization and future expansion with /planner.

Quick Start

Use quick-plan to generate a backlog plan for a new feature idea by inputting its description.

Frequently Asked Questions about quick-plan

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

FAQPage Schema
How do I quickly create a backlog plan from a feature idea?

To quickly create a backlog plan, input your feature description to generate a concise, template-driven planning document. This captures ideas rapidly and stores them using a standard template for future expansion.

What is the best way to scope small features for rapid documentation?

The best way to scope small features is generating lightweight backlog items from brief inputs. This approach speeds up planning and produces starter documents for rapid documentation without heavy overhead.

Does quick-plan require any specific templates to generate backlog plans?

Quick-plan uses a standard backlog template internally to generate backlog plans. You do not need to configure external templates; the process automatically writes your input to the predefined structure.

How are generated backlog plans organized and stored?

Generated backlog plans are organized using date-based filenames and stored in the backlog/plans directory. This automatic naming convention ensures easy organization and quick retrieval for later expansion.

When should I avoid using lightweight backlog planning for feature scoping?

You should avoid lightweight backlog planning for complex feature scoping requiring detailed task breakdowns. This approach is designed for quick, starter backlog items and rapid idea capture rather than comprehensive project planning.