Results for “phases”

Archives phase directories from completed milestones into versioned archive folders, showing a dry-run summary and moving directories only after confirmation.

Provides civil infrastructure and construction domain knowledge, covering materials, project phases, building systems, contracts, site development, and regulatory requirements.

Suggests manual context compaction at logical intervals to preserve context through task phases rather than relying on arbitrary auto-compaction.

Implements a structured problem-solving algorithm that guides every response through observe, think, plan, build, execute, verify, and learn phases toward a defined ideal state.

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

Execute all plans in a phase with wave-based parallelization

Spawns a researcher agent to investigate how to implement a project phase, gathering context on architecture patterns, standard libraries, and common pitfalls.

Diagnose and optimize slow-loading, high-memory, or low-FPS USD scenes using a structured workflow with profiling, validation, and mutation phases.

Identify, test, deploy, and verify software updates across an organization's IT infrastructure using a structured patch management workflow with phased rollouts and automated assessment.

Create detailed phase plan (PLAN.md) with verification loop

Runs a structured 6-phase multi-agent board meeting protocol for strategic decisions, with isolated C-suite contributions, critic analysis, synthesis, founder review, and decision extraction.

Gather phase context through adaptive questioning before planning

Defines a gated Research-Plan-TDD-Review-Commit pipeline for orchestrating feature development, defect fixes, and refactoring tasks through composable phases and human approval gates.

Guides the design and structuring of workflow-based Claude Code skills with multi-step phases, decision trees, subagent delegation, and progressive disclosure.

Coordinates a squad of specialized agents for software development, routing tasks and managing context across requirements, planning, architecture, implementation, review, testing, and deployment phases.

Defines a structured eval-driven development workflow with define, implement, and verify phases, including capability, behavior, and non-functional checks, plus optional swarm mode for parallel evaluation.

Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.

Generate implementation plans from approved designs — plan-generator, phase-based plans, parallel batch execution, task dependency graph, owner skill routing, acceptance criteria, global done criteria, plan frontmatter, layout contract, interaction contract, anti-drift rules, plan format, AD-2 byte-for-byte gate, scope definition, execution plan, phases and batches, task anatomy, plan file format

Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).