plan

Generates an approved implementation plan, spec, and cold-executor handoff from a design document.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill plan-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/jokerman89/lintel/tree/main/skills/plan
Command: npx skills add https://github.com/jokerman89/lintel --skill plan-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump from a design doc straight into coding, leaving implementation unplanned, unestimated, and unreviewed. This Skill turns an approved design document and codebase discovery report into a concrete, reviewable execution plan with task breakdowns, token estimates, and an explicit approval gate before any build work begins. ## Core Features & Use Cases - Cold-executor trio generation: Produces plan.md, spec.md, and prompt.md from versioned templates so a fresh AI session can re-execute the work without prior context. - Task decomposition and work packages: Breaks work into 2-5 minute leaf tasks with file paths, requirement traceability, acceptance criteria, and dependency graphs, grouped into bounded packages. - Mandatory gates and reviews: Enforces a token-estimate gate, cross-section analysis, two-stage adversarial review, and a founder approval pause before BUILD. - Use Case: After finishing a design doc for a new API endpoint, run the planner to get an ordered task list with verification commands, a token estimate, and a self-contained handoff prompt that another session or teammate can execute directly. ## Quick Start Ask the agent to run /li:plan on your approved design document to produce the plan, spec, and executor handoff for review and approval.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a design doc into an implementation plan?▼

Run the plan workflow with your approved design document as input. It reads the design doc and discovery report, decomposes the work into 2-5 minute tasks with file paths and acceptance criteria, and writes plan.md, spec.md, and prompt.md for review.

How to estimate token cost before running an AI coding task?▼

The planning step emits a labelled token estimate based on the work size, marked calibrated or uncalibrated depending on recorded history. It deliberately avoids dollar figures and only shows wall-clock time when explicitly requested.

Can I use the planner standalone without the full cycle?▼

Yes, the planner works as a standalone module when you already have an approved design document. It produces the same plan, spec, and handoff trio and can also be called as a sub-module by other workflows using a --from flag.

Does the planner work with existing Spec Kit artifacts?▼

Yes, it maps existing Spec Kit spec, plan, and tasks files through a shared work-map contract, preserving their structure and task IDs. Existing authorization can approve the mapped scope without recreating tasks.

When should I skip the planning phase?▼

Skip it for hotfixes, trivial edits, or research-only work where no build follows. Planning requires an approved design doc; without one the workflow returns to the define phase instead of proceeding.