Draft a structured PLAN-*.md document with sub-tasks and dependency edges.
npx skills add https://github.com/semanticpixel/abc --skill plan-semanticpixel
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
It helps you turn a feature idea into a structured, downstream-friendly plan without getting stuck in endless clarification loops.
PLAN-<slug>.md on disk within the first few tool calls so you can iterate in the file instead of in chat.Sub-tasks formatted so /abc:scaffold-sub-issues can convert them into Linear parent + sub-issues with repo: labels and dependency edges.blocks / blocked by relationships so /abc:ship-epic can read the dependency graph and ship work in parallel across repos.Open questions and Validation so the next steps are clear and verifiable.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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
pingmepiGenerate a structured 7-section product brief from a business statement.
semanticpixelConvert PLAN-*.md files into Linear parent issues and ordered sub-issues with dependency relations.
menoncelloOrchestrate subagents, commands, MCP servers, and skills with parallel execution.
jg-chalk-ioGenerate structured GitHub issue templates for MoAI projects with standardized sections.