hassan-mohiddin

Use when coordinating Freeflow Pi/cmux pane delegation, orchestrator/planning-parent/execution-parent workflows, task packets, child results, context locality, capability reroutes, multi-agent execution, work packages, worktrees, routing fresh-reviewer/subagent requests, or when the user asks to ...

Use when coordinating Freeflow Pi/cmux pane delegation, orchestrator/planning-parent/execution-parent workflows, task packets, child results, context locality, capability reroutes, multi-agent execution, work packages, worktrees, routing fresh-reviewer/subagent requests, or when the user asks to ...

Use when choosing, changing, or explaining how Freeflow mode applies to current work.

Use after the Workflow, Decision Gate, or Discuss route is clear when choosing between native tools and Freeflow routed tools, retrieving repo/local/vault evidence, transforming bounded evidence, handling unknown-size or broad output, running likely-large/noisy commands, recovering vaulted output...

Review a pull request when asked for code review.

Use when the user asks whether an issue, task, or product decision already exists.

Answer direct user questions before proposing workflow action.

Use when creating, rewriting, tightening, or reviewing an agent skill's instructions, trigger description, structure, examples, or bundled resources.

Use when evaluating, comparing, or making readiness claims about agent-skill behavior.

Use when creating or revising an agent skill.

Capture settled durable decisions into existing owning repo memory, or ask where to record them before creating a destination. Use after discussion, research, specs, reviews, or implementation when the user asks to record decisions, durable memory, glossary terms, ADR-worthy tradeoffs, rejected a...

Use when brainstorming, shaping a feature or task, stress-testing a plan, clarifying product or domain direction, or reaching shared understanding before specs, plans, implementation, or normal non-code decisions.

Use when gathering evidence before a decision, summarizing repo or external facts, checking whether context supports a proposed path, or preparing a brief before specs, plans, brainstorming, or implementation.

Use when the user asks to report and remember the assigned state-isolation probe token.

Use when the user asks to report and remember the assigned state-isolation probe token.

Use when the user explicitly asks to bypass, skip, or reduce workflow ceremony, especially with `/bypass next` or `/bypass task`.

Use when creating a git commit or simple push, deciding whether a verified slice is a coherent rollback checkpoint, inspecting staged, unstaged, untracked, generated, sensitive, or mixed changes, or handling broad “commit everything” pressure.

Use when the next action depends on a user-owned decision, source-truth or path conflict, material method substitution, ambiguous artifact destination, or new evidence from discovery, implementation, review, or verification that makes the current route unsafe or changes the next action.

Use when module, interface, seam, state, role, failure-contract, or test-boundary choices affect complexity and reversibility; when consequential authority, canonical evidence, atomic visibility, or post-commit recovery needs one coherent failure unit; when caller coordination is growing; or when...

Use when asked to investigate or fix a bug, failed test, flaky failure, regression, performance problem, unexpected behavior, or anything described as broken.