Results for “plan-structure”

Load a written implementation plan, execute each task with verification checkpoints, and complete development using a structured workflow.

Creates a structured, non-advisory planning worksheet for prediction-market trade ideas, venue inspection, and manual execution steps.

Generate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.

Plan structured workshops with goals, agenda, activities, prompts, decision rules, and follow-ups.

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

Detect monorepo structure, identify shared chokepoints, and generate safe parallel lane specs aligned to package boundaries

Manage issues, projects, and team workflows in Linear with structured workflows for sprint planning, bug triage, and release management.

Guides a structured feature-development workflow: explore the codebase with subagents, draft a plan for approval, implement step by step, verify with parallel checks, and record conventions.

This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing", "act structure", "story arc", "plot outline", or wants to plan and manage the narrative structure of a story.

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

Plan and facilitate design sprints from challenge framing through prototype testing, using a structured 5-day process with variations for mini, remote, and discovery sprints.

Run structured What-If scenario analysis with 4-6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use for speculative questions about uncertain futures, strategic forks, contingency planning, or stress-testing decisions.

Run a Virtual Think Tank — a structured multi-persona debate — before planning or making architectural/design/strategic decisions. Use this skill whenever the user is about to plan a system, make a technology choice, evaluate trade-offs, decide on an approach, or faces any decision where multiple perspectives would sharpen the outcome. Also trigger when the user says "think tank", "debate this", "perspectives on", "trade-offs", "should I use X or Y", "help me decide", "before we plan", or asks for pros/cons of competing approaches. This skill should run BEFORE any implementation planning begins — it produces a structured analysis that feeds into better plans.

Models cascading what-if scenarios across all business functions to prepare for compound adversity, using a structured six-step framework that maps variables, domain impacts, cascade effects, severity levels, early warning signals, and hedging strategies.

Eng manager-mode plan review. (gstack)

Build a compact, validation-gated implementation plan for multi-step, risky, or ambiguous work — typically when phases need explicit checkpoints, the change touches multiple files/services, or the user wants alignment before execution. Output goes to `.claude/plans/<topic>.md` (or `.agents/plans/`) with goal, in/out-of-scope, phased steps, validation per phase, and replanning triggers. Skip for trivial single-file fixes, bug investigations (use `tracer`), or open-ended exploration (use `explore`). Pair with `ship` once the plan ends and merge work begins.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Design pricing, packaging, and monetization strategy for a software or AI product. Use when the team needs plan structure, free-tier logic, usage vs seat pricing tradeoffs, paywall timing, or monetization guardrails tied to product value and costs.

Design grading plans. TRIGGERS - Use when user needs help with grading-plan related tasks.

Reads a plan document, decomposes it into steps, designs a per-step agent chain from the ECC catalogue, and emits ready-to-paste /orchestrate custom prompts without executing them.

Create comprehensive test plans with coverage and strategy. TRIGGERS - Use when user needs help with test-plan related tasks.

启动一个新的规划流程，创建新的规划文件。

Create game plans with strategy and tactics. TRIGGERS - Use when user needs help with game-plan related tasks.

Design APQP plans for product quality. TRIGGERS - Use when user needs help with apqp-plan related tasks.

Splits a body of context into a sequence of vertical-slice build phases where each phase is independently demonstrable to a real user and each builds on the previous. Use when the user wants to plan, sequence, phase, slice, break down, or order the build of a feature, capability, system, or initiative, and produces a plain-language phased build outline. Does not produce implementation detail — use plan-implementation. Does not specify behavior that has not been decided — use plan-a-feature. Does not perform gap analysis between two artifacts — use gap-analysis. Does not break a plan into independently-grabbable work items — use plan-work-items.

Drafts Family Limited Partnership agreements for estate planning and intergenerational wealth transfer. Ensures IRS enforceability under IRC §2036 with legitimate business purpose, valuation discounts, and senior-generation control. Use when drafting FLP agreements, family partnership documents, or estate planning partnership structures.

Analyze a codebase and generate a structured map of files relevant to a task before making changes.

Analyze a problem, plan the fix, execute with verification. Use when tackling a non-trivial bug, feature, or refactor that needs structured approach.

Drafts a state-compliant Last Will and Testament covering declarations, revocation of prior instruments, specific bequests, residuary disposition, guardian nominations, fiduciary appointments, and execution formalities. Conducts structured intake on family structure, asset inventory, fiduciary nominees, and existing estate plan documents. Coordinates with trusts, beneficiary designations, and non-probate transfers. Use when drafting wills, testamentary documents, pour-over wills, codicils, or estate planning instruments involving testamentary dispositions.

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.