All authors
Claude Skills by hassan-mohiddin
github.com/hassan-mohiddin81 skills0 installs0 views
- NeutralUse 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 spawn/manage visible pane agents.Votes: 0GitHub stars: 3
- Delegation HarnessUse 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 spawn/manage visible pane agents.Votes: 0GitHub stars: 3
- Context VirtualizationUse after broad or noisy tool evidence has been safely narrowed or exhausted, or when an activity boundary leaves raw results that no longer need to remain active.Votes: 0GitHub stars: 3
- Conversation HistoryUse when the next decision requires exact prior conversation wording, rationale, chronology, or provenance that is absent from active context.Votes: 0GitHub stars: 3
- Mode ContractUse when a user asks to set, change, infer, or discuss conversation/workflow/strict-workflow mode, or when task risk suggests recommending a workflow mode.Votes: 0GitHub stars: 3
- Mode ContractUse when choosing, changing, or explaining how Freeflow mode applies to current work.Votes: 0GitHub stars: 3
- Output RouterChoose how evidence moves into context. Freeflow tools are the safe first choice for unknown-size, exploratory, repo-wide, generated/log-adjacent, structured, or likely noisy output, including broad `rg`/`find`/`git`/help/docs scans. Native tools stay direct for known-small, exact, intentionally raw, or mutating work. A post-hoc cap such as `head`, `sed -n`, `tail`, or `wc` does not make a broad producer known-small. Output Router does not classify the task. Workflow, Decision Gate, or Discus...Votes: 0GitHub stars: 3
- Output RouterUse 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, tuning outputRouter/observedRouting/scriptTransform after setup, or handling optional native read/bash safety-net routing.Votes: 0GitHub stars: 3
- Review PrUse when reviewing a pull request or local diff before merge.Votes: 0GitHub stars: 3
- Triage QuestionUse when the user asks whether an issue, task, or product decision already exists.Votes: 0GitHub stars: 3
- Review PrUse when reviewing a pull request or local diff before merge.Votes: 0GitHub stars: 3
- Answer QuestionAnswer direct user questions before proposing workflow action.Votes: 0GitHub stars: 3
- Review PrReview a pull request when asked for code review.Votes: 0GitHub stars: 3
- SkillCreate or revise agent skills. Use when defining a skill's trigger description, active instructions, stop conditions, structure, examples, references, scripts, or readiness status.Votes: 0GitHub stars: 3
- SkillUse when creating, rewriting, tightening, or reviewing an agent skill's instructions, trigger description, structure, examples, or bundled resources.Votes: 0GitHub stars: 3
- Evaluate SkillUse when evaluating, comparing, or making readiness claims about agent-skill behavior.Votes: 0GitHub stars: 3
- Write SkillUse when creating or revising an agent skill.Votes: 0GitHub stars: 3
- Capture DecisionsCapture 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 approaches, scope constraints, or consequential workflow decisions.Votes: 0GitHub stars: 3
- Grill ContextUse 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.Votes: 0GitHub stars: 3
- Research BriefUse 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.Votes: 0GitHub stars: 3
- TddUse when implementing or changing settled behavior test-first, reproducing a bug through regression evidence, or protecting existing behavior before a refactor.Votes: 0GitHub stars: 3
- TddUse when implementing or changing observable behavior test-first, fixing a bug with regression evidence, choosing a test seam for a planned slice, or when a test is hard to write, passes immediately, conflicts with source truth, or starts driving architecture.Votes: 0GitHub stars: 3
- Tool ExecutionUse for Freeflow programs, mutations, exact artifact recovery, and unfamiliar catalog operations; bounded direct read/search needs no skill solely for one call.Votes: 0GitHub stars: 3
- State AlphaUse when the user asks to report and remember the assigned state-isolation probe token.Votes: 0GitHub stars: 3
- State BetaUse when the user asks to report and remember the assigned state-isolation probe token.Votes: 0GitHub stars: 3
- BypassUse when the user explicitly asks to bypass, skip, or reduce workflow ceremony, especially with `/bypass next` or `/bypass task`.Votes: 0GitHub stars: 3
- Commit WorkUse 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.Votes: 0GitHub stars: 3
- Decision GateUse 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.Votes: 0GitHub stars: 3
- Design For DepthUse 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 implementation/review keeps producing edge-case patches, public states, flags, retries, or broad refactors.Votes: 0GitHub stars: 3
- Diagnose FailureUse when asked to investigate or fix a bug, failed test, flaky failure, regression, performance problem, unexpected behavior, or anything described as broken.Votes: 0GitHub stars: 3
- DiscussUse when discussing, exploring, shaping, challenging, or revisiting an idea, request, artifact, design, or implementation direction, or when an open-ended request or new evidence makes the next approach uncertain.Votes: 0GitHub stars: 3
- Execute WorkUse when executing or resuming implementation, fixes, prototypes, documentation updates, repository maintenance, or other concrete changes.Votes: 0GitHub stars: 3
- Finish BranchUse 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.Votes: 0GitHub stars: 3
- HandoffUse 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.Votes: 0GitHub stars: 3
- Launch WorkUse 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.Votes: 0GitHub stars: 3
- Migration WorkUse 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.Votes: 0GitHub stars: 3
- Release WorkUse 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.Votes: 0GitHub stars: 3
- Review ArtifactUse 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.Votes: 0GitHub stars: 3
- Review WorkUse 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.Votes: 0GitHub stars: 3
- Setup FreeflowUse when activating Freeflow in a repository, repairing its repository or personal configuration, or checking whether the current host is delivering Freeflow context.Votes: 0GitHub stars: 3
- Simplify CodeUse 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.Votes: 0GitHub stars: 3
- Track WorkUse 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.Votes: 0GitHub stars: 3
- Verify WorkUse 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.Votes: 0GitHub stars: 3
- WorkflowUse for consequential work that may involve discovery, decisions, specification, planning, implementation, diagnosis, review, verification, commits, handoffs, or route changes from new evidence.Votes: 0GitHub stars: 3
- Write PlanUse when writing or revising an implementation plan, execution plan, remediation plan, migration plan, or similar ordered plan.Votes: 0GitHub stars: 3
- Write SpecUse when turning settled discovery, explicit requirements, validated design direction, or source evidence into a durable behavioral, technical, API, migration, or decision specification that later planning and review can rely on.Votes: 0GitHub stars: 3
- Qualification BaseUse when an evaluation prompt explicitly asks for a bounded artifact or response.Votes: 0GitHub stars: 3
- Composition BaseUse when a task asks for the declared composition marker or exercises the synthetic adapter fixture.Votes: 0GitHub stars: 3
- Evidence BaseUse when the synthetic adapter fixture asks to close a route or state remaining evidence.Votes: 0GitHub stars: 3
- Marker CandidateUse when a task asks for the declared composition marker.Votes: 0GitHub stars: 3