Skill Creator
cipherstash
31 published skills · 62 GitHub stars across the catalog. View on GitHub ↗
algorithmic-command-enforcement
Use boolean decision trees instead of imperatives for 100% compliance under pressure
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
capturing-learning-from-completed-work
Systematic retrospective to capture decisions, lessons, and insights from completed work
commit-workflow
Systematic commit process with pre-commit checks, atomic commits, and conventional commit messages
conducting-code-review
Complete workflow for conducting thorough code reviews with structured feedback
creating-quality-gates
Establish workflow boundary checklists with clear pass/fail criteria and escalation procedures
creating-research-packages
Document complex domain knowledge as self-contained packages with multiple reading paths
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
documenting-debugging-workflows
Create symptom-based debugging documentation that matches how developers actually search for solutions
dual-verification
Use two independent agents for reviews or research, then collate findings to identify common findings, unique insights, and divergences
executing-plans
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
finishing-a-development-branch
Use 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 cleanup
following-plans
Algorithmic decision tree for when to follow plan exactly vs when to report BLOCKED - prevents scope creep and unauthorized deviations
maintaining-documentation-after-code-changes
Two-phase workflow to keep project documentation synchronized with code changes
organizing-documentation
Set up or reorganize project documentation using intent-based structure (BUILD/FIX/UNDERSTAND/LOOKUP)
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches cipherpowers:code-review-agent subagent to review implementation against plan or requirements before proceeding
revising-findings
Implement findings from verification reports with scope-based parallel workflow
selecting-agents
Decision guide for choosing the right specialized agent for each task type
sharing-skills
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
systematic-type-migration
Safe refactoring workflow for replacing old types with new type-safe implementations through integration-test-first, file-by-file migration with incremental verification
tdd-enforcement-algorithm
Algorithmic decision tree enforcing test-first development via boolean conditions instead of imperatives
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first