don-smith/myflow

Use after a passing MyFlow Verify report to make proportionate closeout decisions, preserve continuity, and decide delivery with the developer.

Use when reviewing a branch, commit range, pull request, or work-in-progress change against its specification and repository standards.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Create structured atomic commits. Use when the user asks to commit, or when Implement has completed a plan phase whose automated success criteria are green.

Resolve material architectural decisions for a MyFlow workstream and write a standalone design artifact only when Scope or Plan requires structural design. Use after Scope and selected research/specialists, before Plan.

Use when behavior is broken, failing, flaky, unexpectedly slow, or otherwise differs from its expected result, before proposing a durable fix.

Extract feature intent and requirements through grill-me rounds when Scope cannot state the outcome and acceptance criteria clearly enough. Supports light ideation for a fuzzy concept and structured requirements extraction for complex work. Writes a requirements artifact into the workstream and returns to scope.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, or when another skill needs to maintain the domain model.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, when a skill needs collaborative decision-making, or on any 'grill' trigger phrase.

Write or resume a lightweight handoff document for a session transition. Write mode compacts the current task, decisions, in-flight changes, and next steps into a concise file; resume mode reads one back and continues the work. Use when context is large and you need to pause mid-stage, or when a fresh session starts from such a pause. Artifacts are the primary handoff mechanism — this is a backup for mid-stage pauses.

Use when executing an accepted MyFlow implementation plan phase by phase in a fresh or resumed implementation session.

Use when starting or navigating work that should follow the MyFlow five-stage, artifact-led development workflow

Use when introducing MyFlow to a repository, refreshing repository workflow knowledge, or when a MyFlow skill lacks a required repository path or convention.

Produce the accepted, executable implementation plan for a MyFlow workstream. Accepts an alignment artifact for lightweight work or a standalone design artifact for structural work.

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Investigate a specific codebase or external question selected by a MyFlow workstream, record evidence in the workstream, and return to Scope, Design, or Plan with a recommendation.

Begin a MyFlow workstream with right-sized, code-light scoping. Establishes a workstream ID and durable alignment artifact when needed, selects only the specialists the work requires, and offers an isolated worktree or trunk-based path.

Use during design and planning to shape testable interfaces, seams, and verification strategy; use during implementation when a plan needs a test-first behavior cycle

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

Use after Implement to verify an accepted MyFlow plan, collect review evidence, and produce a workstream-aware Verify report.