All authors
Claude Skills by lsy041015
github.com/lsy04101516 skills0 installs6 views
- BrainstormingUse when starting a new project or large feature, or when a change needs unresolved design decisions. Skip read-only tasks and straightforward changes with settled requirements.Votes: 0GitHub stars: 2
- Diagnosing OrchestraUse when the user asks to diagnose or investigate an Orchestra session that repeated work, ignored a plan, stumbled, produced poor results, or used unexpected time or tokensVotes: 0GitHub stars: 2
- Dispatching Parallel AgentsUse only when the user explicitly requests independent implementation work that can run concurrently without shared stateVotes: 0GitHub stars: 2
- Executing PlansUse when an approved implementation plan should be executed in the current session without delegated task workersVotes: 0GitHub stars: 2
- Finishing A Development BranchUse when implementation is complete, all tests pass, and you need to decide how to integrate the workVotes: 0GitHub stars: 2
- OrchestratorUse in Claude Code when a plan the user approved or asked to execute should be split into difficulty tiers and each tier delegated to a Claude subagent, or to a Codex CLI worker only when the user asks for Codex. Not for Codex-hosted sessions.Votes: 0GitHub stars: 2
- Receiving Code ReviewUse when review feedback arrives and its correctness, scope, or implementation impact must be evaluatedVotes: 0GitHub stars: 2
- Requesting Code ReviewUse when a completed change needs a requirements and quality review before the next task or integrationVotes: 0GitHub stars: 2
- Subagent Driven DevelopmentUse when an approved implementation plan has a clear unit that can be delegated to an implementation worker. In Claude Code, load it together with orchestra:orchestratorVotes: 0GitHub stars: 2
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 2
- Test Driven DevelopmentUse when adding or changing program behavior, fixing a bug, or refactoring behavior that needs regression protection.Votes: 0GitHub stars: 2
- Using Git WorktreesUse when an authorized coding task needs an isolated checkout. Reuse existing isolation; small safe edits do not require a worktree.Votes: 0GitHub stars: 2
- Using OrchestraUse when the user names Orchestra or asks for its plan, delegate and review workflow. Skip unrelated conversations and simple lookups.Votes: 0GitHub stars: 2
- Verification Before CompletionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires traceable verification evidence before success claimsVotes: 0GitHub stars: 2
- Writing PlansUse when a settled design needs multiple verifiable implementation steps. Skip ceremonial plans for obvious small changes.Votes: 0GitHub stars: 2
- Writing SkillsUse when creating, editing, or verifying a skill before it is enabled or deployedVotes: 0GitHub stars: 2