weave-it

Execute selected local Weave tasks for an active change by preparing branches, implementing tasks, running verification, and updating tasks.md evidence without committing, pushing, or opening PRs.

Chat-driven bug-fix entry point that creates a fix-type change, writes findings.md, and scaffolds a single task-slice folder.

Scaffold task-slices folders from upstream artifacts using tracer-bullet vertical slices, per-slice tasks, and slice-level technical contracts.

Execute selected local Weave tasks for an active change by preparing branches, implementing tasks, running verification, and updating tasks.md evidence without committing, pushing, or opening PRs.

Chat-driven bug-fix entry point that creates a fix-type change, writes findings.md, and scaffolds a single task-slice folder.

Scaffold task-slices folders from upstream artifacts using tracer-bullet vertical slices, per-slice tasks, and slice-level technical contracts.

Read-only thinking partner for active Weave architecture work. Use when the user wants engineering architecture, technical design, implementation strategy, tradeoff analysis, risk review, or a deep dive into an existing architecture facet.

Capture the current discussion into a structured session note for a Weave change, optionally updating the active change artifact.

Stress-test product requirements against the current system, workflows, and domain language. Use when refining PRDs, validating workflows, uncovering edge cases, clarifying ownership, or aligning new changes with existing product behavior.

Answer what to do next for the active Weave change by inspecting artifact state and resume notes without mutating files.

Generate or revise prd.md for an active Weave change. Use when the user wants to convert exploration, discussion, sessions, or product interview context into a product requirements document.

Prepare task execution branches for an active Weave change without implementing, verifying, committing, pushing, or opening PRs.

Clarify and revise one existing Weave change artifact without advancing the workflow. Use when scope, requirements, assumptions, or decisions change midstream and an existing exploration.md, prd.md, findings.md, or architecture.md needs amendment.

Update current-state Weave knowledge specs and change-local knowledge delta for an active change.

Start a new Weave change exploration from a title or topic. Use when the user wants to begin capturing a change under wiki/changes and create the matching change branch.