Maintaining Documentation After Code Changes
Two-phase workflow to keep project documentation synchronized with code changes
TDD Enforcement Algorithm
Algorithmic decision tree enforcing test-first development via boolean conditions instead of imperatives
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
using-git-worktrees
Use 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 verification
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
Documenting Debugging Workflows
Create symptom-based debugging documentation that matches how developers actually search for solutions
testing-skills-with-subagents
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
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
Algorithmic Command Enforcement
Use boolean decision trees instead of imperatives for 100% compliance under pressure
Conducting Code Review
Complete workflow for conducting thorough code reviews with structured feedback
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
Validating Review Feedback
Validate code review feedback against implementation plan to prevent scope creep and derailment
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
following-plans
Algorithmic decision tree for when to follow plan exactly vs when to report BLOCKED - prevents scope creep and unauthorized deviations
dual-verification
Use two independent agents for reviews or research, then collate findings to identify common findings, unique insights, and divergences
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
Commit Workflow
Systematic commit process with pre-commit checks, atomic commits, and conventional commit messages
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
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
using-cipherpowers
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
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
revising-findings
Implement findings from verification reports with scope-based parallel workflow
Organizing Documentation
Set up or reorganize project documentation using intent-based structure (BUILD/FIX/UNDERSTAND/LOOKUP)
Conducting Plan Review
Complete workflow for evaluating implementation plans before execution with quality checklist and structured feedback
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