plan

Draft a structured PLAN-*.md document with sub-tasks and dependency edges.

Updated May 20, 2026

Search Tags:#planning #documentation #workflow automation #Linear #dependency graph #issue scaffolding #multi-repo shipping

Ready to run

npx skills add https://github.com/semanticpixel/abc --skill plan-semanticpixel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/plan
Command: npx skills add https://github.com/semanticpixel/abc --skill plan-semanticpixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a feature idea into a structured, downstream-friendly plan without getting stuck in endless clarification loops.

Core Features & Use Cases

Writes-first PLAN docs: Produces a PLAN-<slug>.md on disk within the first few tool calls so you can iterate in the file instead of in chat.
Sub-task structure for issue scaffolding: Creates Sub-tasks formatted so /abc:scaffold-sub-issues can convert them into Linear parent + sub-issues with repo: labels and dependency edges.
Parallel shipping readiness: Designs blocks / blocked by relationships so /abc:ship-epic can read the dependency graph and ship work in parallel across repos.
Decision-oriented output: Includes Open questions and Validation so the next steps are clear and verifiable.

Quick Start

Use the plan skill to generate a draft plan for “Add a settings page to the dashboard” so you can then scaffold Linear issues from the resulting PLAN file.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I draft a structured plan document for feature development without endless clarifying questions?▼

Drafting a structured plan document requires writing a local PLAN-*.md file with sections for context, approach, sub-tasks, open questions, and validation. This workflow bootstraps downstream issue creation with minimal clarifying questions for fast deliverables.

How do I scaffold Linear issues and sub-tasks from a planning document?▼

Scaffolding Linear issues requires a plan document with a specific sub-task structure. The PLAN file formats sub-tasks so downstream commands can convert them into Linear parent and sub-issues, automatically applying repository labels and dependency edges.

What is the best way to plan parallel shipping across multiple repositories?▼

Parallel shipping across repositories requires a dependency graph with blocks and blocked-by relationships. A structured plan document designs these edges so downstream tools can read the graph and execute work in parallel across different repos.

Can I use this planning workflow for migrations and refactors, or is it only for new features?▼

This planning workflow supports feature, migration, and refactor planning workflows. It generates a structured plan document that establishes context, approach, and validation steps for any technical deliverable needing structured execution.

What sections are needed in a plan document to ensure downstream parallel execution?▼

A plan document needs sections for context, approach, sub-tasks, open questions, and validation. Sub-tasks must include repository labels and dependency edges to ensure downstream tools can execute work in parallel across repositories.

Does this planning approach write the plan directly to disk or keep it in chat?▼

This planning approach writes first by producing a PLAN-<slug>.md file on disk within the first few tool calls. This allows you to iterate directly in the local file instead of managing the plan in chat.