All authors

Claude Skills by DollarDill
github.com/DollarDill22 skills0 installs62 views
- Auditing Upstream DriftUse when checking if beads-superpowers is outdated, before a plugin release, or when auditing for missing capabilities — covers upstream drift, test execution, documentation, plugin health, and content integrityVotes: 0GitHub stars: 26
- BrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 26
- Dispatching Parallel AgentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesVotes: 0GitHub stars: 26
- Document ReleaseUse after code changes are committed but before PR merge to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG, CLAUDE.md, TODOS, and VERSION files. Triggers on "update docs", "sync documentation", "post-ship docs", "document release", "documentation audit".Votes: 0GitHub stars: 26
- Executing PlansUse when you have a written implementation plan to execute in a separate session with review checkpointsVotes: 0GitHub stars: 26
- Finishing A Development BranchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupVotes: 0GitHub stars: 26
- Getting Up To SpeedUse at the start of a session, after compaction, or whenever you need to orient on an unfamiliar or stale codebase. Loads beads context, deep-dives the codebase, and produces a structured 'current state' summary. Triggers on phrases like "catch me up", "where are we", "orient me", "what's the state of this project", "bring me up to speed", "load context", "session orientation".Votes: 0GitHub stars: 26
- Project InitUse when beads/Dolt database initialization fails, when bd commands return errors about missing databases, when setting up beads in a new project, or when recovering from diverged Dolt history. Handles fresh init, bootstrap from remote, and recovery workflows.Votes: 0GitHub stars: 26
- Receiving Code ReviewUse 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: 26
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsVotes: 0GitHub stars: 26
- Research Driven DevelopmentUse when the user asks a question about a topic, requests research, or when you need to understand something before planning. Dispatches parallel research agents, synthesizes findings into a persistent document, and writes it to the project's research directory. Triggers on "research this", "what is X", "how does Y work", "compare A vs B", "investigate", "deep dive", "look into".Votes: 0GitHub stars: 26
- Stress TestUse when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when brainstorming/writing-plans suggests review.Votes: 0GitHub stars: 26
- Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionVotes: 0GitHub stars: 26
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 26
- Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 26
- Using Git WorktreesUse 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: 26
- Using SuperpowersUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questionsVotes: 0GitHub stars: 26
- Verification Before CompletionUse 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: 26
- Write DocumentationUse when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.Votes: 0GitHub stars: 26
- Writing PlansUse when you have a spec or requirements for a multi-step task, before touching codeVotes: 0GitHub stars: 26
- Memory CuratorUse at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".Votes: 0GitHub stars: 26
- Session HandoffA human-invoked utility that writes a grounded session-handoff document (plus a continuation pointer memory) so a fresh agent can resume in-progress work. Not auto-invoked; a human runs it deliberately.Votes: 0GitHub stars: 26