All authors
Claude Skills by Codoop
github.com/Codoop12 skills0 installs32 views
- Codoop DiscoverLaunch a collaborative product discovery session with multi-role experts (PM, GTM, UI, Architect). Use when exploring 0-to-1 design for a new product or feature. Orchestrates expert agents in-session to draft comprehensive backlog documentation through SNAP clarification, multi-perspective analysis, and consistency auditing.Votes: 0GitHub stars: 5
- Codoop ExecuteDrive the codoop-flow Agent-Centric ticket pipeline in-session from Codex, Claude Code, or another coding agent. Use when the user asks to run tickets, process the pending queue, or work a specific ticket through build/verify/review/ship. Orchestrates the plugin-level deterministic Runtime plus the current agent's coding, review, and self-healing work.Votes: 0GitHub stars: 5
- Codoop InitInspect an existing repository or create selected empty project directories, then initialize or refresh codoop-flow configuration and existing-page UI snapshots. Use when setting up codoop-flow, when existing backend/web/desktop/mobile directories use custom names, when a standalone client lives at the repository root, or when starting a new empty multi-project repository.Votes: 0GitHub stars: 5
- Codoop TicketDesign work tickets (PRD → Spec → Plan) in three stages. It first researches comparable products, recommends a project-specific direction, and grills requirements one decision at a time before orchestrating PM and Architect agents. Its terminal responsibility is promoting an approved ticket to pending/; it never executes the ticket.Votes: 0GitHub stars: 5
- Codoop Ux WalkthroughSimulate a real task from a chosen user persona and write an evidence-backed, non-blocking experience report. Use after building a user-facing feature, when reviewing a runnable product flow, or when product owners want user-perspective improvement ideas without changing code automatically.Votes: 0GitHub stars: 5
- Debugging And Error RecoveryGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.Votes: 0GitHub stars: 5
- Definition Of DoneProject-level completion standard checklist. Every task must meet these criteria before completion—includes code quality, test coverage, documentation, security, and ship-readiness checks.Votes: 0GitHub stars: 5
- GrillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.Votes: 0GitHub stars: 5
- Incremental ImplementationDelivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.Votes: 0GitHub stars: 5
- Planning And Task BreakdownBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Votes: 0GitHub stars: 5
- Spec Driven DevelopmentCreates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.Votes: 0GitHub stars: 5
- Test Driven DevelopmentDrives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.Votes: 0GitHub stars: 5