Showing 52591–52604 of 52604 skills
Use when executing or resuming implementation, fixes, prototypes, documentation updates, repository maintenance, or other concrete changes.
hassan-mohiddin/freeflow
Use when work on a branch or isolated checkout has reached a stopping point and the next job is to inspect integration readiness, choose merge/PR/keep/discard, verify the integrated result, or clean up branch/worktree state safely.
hassan-mohiddin/freeflow
Use when pausing, compacting, transferring, or resuming consequential work; when current context cannot safely finish the next slice; or when a temporary or durable continuation checkpoint must preserve evidence, decisions, route changes, and the next executable horizon for a fresh context.
hassan-mohiddin/freeflow
Use when preparing, approving, executing, monitoring, or rolling back a production deployment or user rollout; defining launch readiness, staged exposure, migration ordering, operational signals, advance/hold/abort criteria, or post-launch verification.
hassan-mohiddin/freeflow
Use when replacing, sunsetting, or removing an API, feature, dependency, schema, configuration, service, or implementation; migrating callers, users, traffic, or data; defining compatibility and rollback; or proving that legacy behavior can be removed safely.
hassan-mohiddin/freeflow
Use when preparing, cutting, publishing, or verifying a versioned software or package release; choosing version impact, updating consumer-facing release notes, producing and signing artifacts, creating tags, or reconciling version, tag, source, and published artifact identity.
hassan-mohiddin/freeflow
Use when reviewing whether a spec, plan, decision note, discovery checkpoint, handoff, or other durable artifact is fit to guide future work; when adjudicating artifact-review findings; or when handling follow-up reviews and repeated artifact-review loops.
hassan-mohiddin/freeflow
Use when reviewing completed work, checking a change before merge or handoff, preparing review context, receiving or applying review feedback, running a follow-up review, deciding whether findings block progress, or handling a repeated review loop.
hassan-mohiddin/freeflow
Use when activating Freeflow in a repository, repairing its repository or personal configuration, or checking whether the current host is delivering Freeflow context.
hassan-mohiddin/freeflow
Use when working code should be made easier to understand, modify, test, or debug without changing accepted behavior; when removing accidental complexity, duplication, indirection, dead abstractions, or confusing control flow; or when review asks for behavior-preserving simplification.
hassan-mohiddin/freeflow
Use when creating, resuming, or updating a durable Working Record so ongoing task state, planned actions, decisions, history, and the next action survive execution, pauses, or context loss.
hassan-mohiddin/freeflow
Use after a meaningful work slice and before claiming work is done, fixed, passing, implemented, reviewed, or ready; when choosing evidence for a claim; when verification fails or proves less than expected; or when verification evidence may change the current route.
hassan-mohiddin/freeflow
Use for consequential work that may involve discovery, decisions, specification, planning, implementation, diagnosis, review, verification, commits, handoffs, or route changes from new evidence.
hassan-mohiddin/freeflow
Use when writing or revising an implementation plan, execution plan, remediation plan, migration plan, or similar ordered plan.
hassan-mohiddin/freeflow