hassan-mohiddin/freeflow

Use when choosing or bounding an environment interaction, especially when the needed context, target, observer, or scope is uncertain, output may be broad, or recent actions have not advanced the current question.

Use when the user explicitly asks to skip or reduce optional workflow pressure for the next authorized activity or the current task.

Use when creating an explicitly requested or selected local Git commit, including staging its exact contents, verifying the resulting checkpoint, or performing a separately authorized simple push.

Use when proceeding would silently choose a consequential outcome for the user, or when accepted sources conflict in a way that leaves one material choice blocking the next action.

Use during coding and software design to keep boundaries, interfaces, ownership, state, dependencies, and failure behavior simple and proportionate.

Use when a bug, failure, regression, performance problem, or repeated unsuccessful correction lacks a supported cause.

Use when exploring, clarifying, or revisiting what to accomplish or how to approach it, especially when user collaboration, alternatives, assumptions, or new evidence could change the next action.

Use when evaluating or comparing agent-skill behavior.

Use when preparing and carrying out requested or approved concrete work, including implementation, fixes, prototypes, documentation, configuration, and repository maintenance.

Use when deciding how to integrate, preserve, or discard work on a branch or isolated checkout.

Use when work must continue safely after a pause, context change, or ownership transfer.

Use when preparing or carrying out a production deployment, rollout, rollback, or recovery.

Use when replacing an existing software or data path and moving its consumers, state, or traffic safely.

Use when preparing, publishing, or verifying a versioned software release.

Use when judging whether a durable artifact is aligned, sufficient, and fit to guide its intended use through self-review, independent review, or adjudication of a returned artifact review.

Use when judging implementation or integrated work through self-review or independent review, or when adjudicating a returned independent review report.

Use when activating Freeflow in a repository, repairing its repository or personal configuration, or checking whether the current host is delivering Freeflow context.

Use when working code should become easier to understand or change without altering accepted behavior, including removing duplication, indirection, dead abstractions, or confusing control flow.

Use when ongoing work needs durable task memory, or when creating, recovering, maintaining, transitioning, or closing a Working Record.

Use when verifying work or a claim after implementation, tests, builds, runtime checks, failures, conflicting evidence, or incomplete evidence.

Use when authority, current ownership, readiness to act, route changes, continuity, selected checkpoints, or Supported Exit must be coordinated across Freeflow activities.

Use when writing or revising an implementation plan, execution plan, remediation plan, migration plan, or similar ordered plan.

Use when creating or revising an agent skill.

Use when writing or revising a spec, PRD, issue, API contract, technical design, migration contract, decision artifact, or similar durable document.