Results for “plan-structure”

Guides a structured planning pipeline for coding tasks, including scope detection, research, plan creation, and review.

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Use this when a Python repository needs package-level planning, import boundaries, module naming, reusable library extraction, or distribution-friendly structure.

Guides a structured planning pipeline for coding tasks, from scoping and research to plan creation, review, and handoff.

Creates detailed, bite-sized implementation plans from specs or requirements, with file structure, task decomposition, and TDD steps.

Creates a concise, actionable plan for coding tasks by scanning context and producing a structured checklist.

Generates complete, copy-paste ready implementation documentation from a PR plan, including code blocks and verification checklists.

Executes a predefined implementation plan step by step, updating progress inline and running build or test commands.

Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).

Structures user research — planning sessions, synthesizing findings, and translating insights into product decisions. Use when planning user interviews, analyzing research data, creating personas or journey maps, or turning qualitative feedback into structured recommendations.

Imports external plan files into a GSD-structured project, detecting conflicts against existing roadmap, requirements, and locked decisions before writing a validated PLAN.md.

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

Structures company knowledge bases for business plan automation, defining a 7-category schema, completeness scoring, and storage layouts for Notion or local Markdown.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization. Use PROACTIVELY for content structuring.

Plan website page hierarchy, navigation, URL patterns, and internal linking for improved SEO and user experience.

Eng manager-mode plan review. (gstack)

Audit, redesign, or plan website structure, URL hierarchy, navigation, and internal linking to improve SEO and user experience.

Creates a strategic SEO plan for new or existing websites, covering competitive analysis, site architecture, content strategy, technical foundation, and a phased implementation roadmap.

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.

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".

Builds a strategic SEO plan for new or existing websites, covering competitive analysis, site architecture, content strategy, technical foundation, and a phased implementation roadmap.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not design the contract for an interface — use design-an-api. Does not research open-ended options before there is a feature to specify — use research.

Designing, optimizing, and auditing repository structure: directory design, docs/ layout (PRD, specs, ADR), test/script organization, anti-pattern detection. Use for repo layout or migration planning.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Plans interface structure, component layout, and interaction details for product flows before implementation.