Results for “construction-plan”

Generates a step-by-step construction plan from a one-line objective, where each step is self-contained and executable by a fresh agent in a new session.

Turns a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects, with self-contained context briefs, adversarial review, and dependency graphs.

Turns a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects, with self-contained context briefs, adversarial review, and dependency graphs.

Generate a step-by-step construction plan from a one-line objective, with dependency graphs, parallel step detection, and adversarial review for multi-session engineering projects.

Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.

Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.

Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.

Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.

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

Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

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.

Structured planning methodology with research, brainstorming, phased plan creation, risk assessment, and plan-to-build continuity.

Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

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

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

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).

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

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

Turn a one-line objective into a step-by-step construction plan any coding agent can execute cold. Each step has a self-contained context brief — a fresh agent in a new session can pick up any step without reading prior steps.

Create project plan using project-planner agent. No code writing - only plan file generation.

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

Writes an actionable markdown implementation plan to .hermes/plans/ without executing code, using bite-sized tasks, exact paths, and complete code examples.

Collaborates with users to design structured development plans broken into testable commits, with research and clarification steps.

Eng manager-mode plan review. (gstack)

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

Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.

Use when you have a spec or requirements for a multi-step task, before touching code

Write construction bid proposals with scope and pricing. TRIGGERS - Use when user needs help with bid-proposal related tasks.