Results for “planning”

Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.

The English summary is being prepared. Showing the original description.

Deadline management and capacity planning across epics and PRs. Use when the user runs /triage or wants deadline/capacity triage.

The English summary is being prepared. Showing the original description.

Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.

The English summary is being prepared. Showing the original description.

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and re-architecture of existing systems. Use PROACTIVELY for database architecture, technology selection, or data modeling decisions.

The English summary is being prepared. Showing the original description.

Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies.

The English summary is being prepared. Showing the original description.

Plan and sequence complex implementation work into deterministic, testable steps. Use when the user asks for planning, roadmap breakdown, execution strategy, effort estimation, or multi-step delivery coordination across domains.

The English summary is being prepared. Showing the original description.

Plan and sequence complex implementation work into deterministic, testable steps for this repository. Use when the user asks for planning, roadmap breakdown, execution strategy, effort estimation, or multi-step delivery coordination across domains.

The English summary is being prepared. Showing the original description.

Execute a trivial task inline — no subagents, no planning overhead

The English summary is being prepared. Showing the original description.

Create a clean PR branch by filtering out .planning/ commits — ready for code review

The English summary is being prepared. Showing the original description.

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

The English summary is being prepared. Showing the original description.

Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

The English summary is being prepared. Showing the original description.

Query, inspect, or refresh codebase intelligence files in .planning/intel/

The English summary is being prepared. Showing the original description.

Surface the agent's assumptions about a phase approach before planning

The English summary is being prepared. Showing the original description.

Build, query, and inspect the project knowledge graph in .planning/graphs/

The English summary is being prepared. Showing the original description.

Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format

The English summary is being prepared. Showing the original description.

Diagnose planning directory health and optionally repair issues

The English summary is being prepared. Showing the original description.

Create an isolated workspace with repo copies and independent .planning/

The English summary is being prepared. Showing the original description.

Builds a structured ransomware incident response playbook aligned with the CISA StopRansomware Guide and NIST Cybersecurity Framework. Covers preparation, detection, containment, eradication, recovery, and post-incident phases with actionable checklists. Activates for requests involving ransomware response planning, CISA compliance, incident response playbook creation, or ransomware preparedness assessment.

The English summary is being prepared. Showing the original description.

Clarify a concrete requirements decision, create one bounded static interview packet, or run an explicitly user-invoked frontier batch over a plan, decision, or idea; trigger on explicit grill/interview/refinement intent or a named material ambiguity, not on ordinary planning, implementation, research, test-plan, report-style review, or BUILD work.

The English summary is being prepared. Showing the original description.

Break a clear scope or accepted specification into ordered tasks/packages when the user explicitly asks for a plan, estimate, dependency order, or task breakdown; do not trigger for ordinary implementation, every multi-step task, speculative parallelism, review, or completion.

The English summary is being prepared. Showing the original description.

Produces comprehensive system architecture plans for features and products including component breakdown, data flow diagrams, system boundaries, API contracts, and scaling considerations. Use for "system design", "architecture planning", "feature design", or "technical specs".

The English summary is being prepared. Showing the original description.

Plans safe API evolution with versioning strategies, client migration guides, deprecation timelines, and backward compatibility considerations. Use for "API versioning", "deprecation planning", "API evolution", or "breaking changes".

The English summary is being prepared. Showing the original description.

Creates comprehensive disaster recovery procedures with automated backup scripts, restore procedures, validation checks, and role assignments. Use for "database backup", "disaster recovery", "data restore", or "DR planning".

The English summary is being prepared. Showing the original description.

Use when designing a Spark feature or writing or materially revising a design proposal that needs repository-first research, user input on unresolved key choices, and an owner-aligned implementation plan before code changes.

The English summary is being prepared. Showing the original description.