All authors
Claude Skills by mzored
github.com/mzored23 skills1 installs16 views
- Brainstorming CodexYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Codex-backed variant.Votes: 0GitHub stars: 7
- Dispatching Parallel Agents CodexUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesVotes: 0GitHub stars: 7
- Finishing A Development Branch CodexComplete development work with Codex-backed branch analysis and structured finish options. Use only when the user explicitly asks for the Codex-backed branch finishing workflow.Votes: 0GitHub stars: 7
- Receiving Code Review CodexUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationVotes: 0GitHub stars: 7
- Requesting Code Review CodexRequest a high-signal Codex-backed review of a diff or task result. Use when completing tasks, implementing major features, or before merging. Codex-backed variant.Votes: 0GitHub stars: 7
- Subagent Driven Development CodexExecute an implementation plan by dispatching Codex-backed implementer and reviewer agents while Claude keeps spec-compliance control. Codex-backed variant.Votes: 0GitHub stars: 7
- Systematic Debugging CodexSystematic 4-phase debugging with Codex-backed root cause investigation. Use only when the user explicitly asks for the Codex-backed debugging workflow.Votes: 0GitHub stars: 7
- Test Driven Development CodexEnforce strict test-driven development via Codex-backed implementation. Use only when the user explicitly asks for the Codex-backed TDD workflow.Votes: 0GitHub stars: 7
- Using Git Worktrees CodexUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verificationVotes: 0GitHub stars: 7
- Verification Before Completion CodexUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysVotes: 0GitHub stars: 7
- Writing Plans CodexUse when you have a spec or requirements for a multi-step task, before touching code. Codex-backed variant.Votes: 0GitHub stars: 7
- BrainstormingUpstream fixtureVotes: 0GitHub stars: 7
- Requesting Code ReviewUpstream fixtureVotes: 0GitHub stars: 7
- Subagent Driven DevelopmentUpstream fixtureVotes: 0GitHub stars: 7
- Writing PlansUpstream fixtureVotes: 0GitHub stars: 7
- Init DeepDeeply analyze a codebase and generate multi-agent project documentation (AGENTS.md + CLAUDE.md + GEMINI.md + scoped docs). Only invoke when user explicitly types /init-deep.Votes: 0GitHub stars: 6
- DogfoodCheck how SkipHow actually behaved in a real session, using the owner's own transcripts. Use when asked why a run misbehaved, whether a plugin version works, where the time or tokens went, or to turn something observed in real use into a change to the shipped skill, weighed against how comparable projects solve it. For developing SkipHow in this repository only.Votes: 0GitHub stars: 4
- SkiphowAct as an adaptive virtual CTO for a founder or product owner. Use for any current-project outcome, including questions, research, reviews, bugs, ideas, features, iterations, lists, programmes, status, unfinished work, cleanup, delivery, process problems, pauses, resumes, and enabling, checking, or disabling SkipHow itself. The owner keeps product decisions; the agent owns the technical lifecycle through verified completion. If context was compacted while this skill governed, reopen this file...Votes: 0GitHub stars: 4
- Skiphow BugInvestigate and repair a reported defect at its root cause, covering the general case and affected sibling paths. Use for bug fixes and recurring failures; keep diagnosis-only requests read-only. If context was compacted while this workflow governed, reopen this file and the SkipHow CTO skill before the next consequential action.Votes: 0GitHub stars: 4
- Skiphow Deploy ReadyPrepare agreed changes for delivery with deferred checks, review, commits, and authorized integration. Use for deploy-ready, release preparation, or clean at the end of an iteration session. Also carry an explicitly authorized deploy prod through verified release; preparation alone grants no production action. If context was compacted while this workflow governed, reopen this file and the SkipHow CTO skill before the next consequential action.Votes: 0GitHub stars: 4
- Skiphow Fast FixesCoordinate a live stream of local fixes and feedback before delivery, across interfaces, services, scripts, configuration, and artifacts. Use for bounded changes that may arrive while others run, with proportional delegation, focused checks, and recoverable shown results. A request to ship uses the delivery workflow. If context was compacted while this workflow governed, reopen this file and the SkipHow CTO skill before the next consequential action.Votes: 0GitHub stars: 4
- Skiphow LongrunDeliver an accepted epic, milestone, or issue set through delegated implementation and independent review loops. Use for sustained execution and resumes of tracked work, with CTO sequencing, integration, and process diagnosis. If context was compacted while this workflow governed, reopen this file and the SkipHow CTO skill before the next consequential action.Votes: 0GitHub stars: 4
- Skiphow PlanPrepare the whole requested scope for implementation with research, a completed product interview, a reviewed specification, bounded tasks, and an execution prompt suited to its size. Explicit invocation requests durable planning records; ordinary read-only planning stays read-only. Stop before implementation. If context was compacted while this workflow governed, reopen this file and the SkipHow CTO skill before the next consequential action.Votes: 0GitHub stars: 4