merge-docs
Merge Design Documents
Goal: Produce a single, unified set of feature docs from two separate designs for the same feature.
When to Use
You have two feature directories under /docs/wip/ for the same feature — each with its own design, implementation plan, and task list — and you need to combine them into one coherent set of docs.
Workflow
See merge-process.md.
More from serpro69/claude-toolbox
cove
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
1analysis-process
Turn the idea for a feature into a fully-formed PRD/design/specification and implementation-plan. Use when you have a spec or requirements that needs implementation. Use in pre-implementation (idea-to-design) stages to make sure you understand the spec/requirements and ensure you have a correct implementation plan before writing actual code.
1testing-process
Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.
1documentation-process
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix
1solid-code-review
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
1development-guidelines
Use when writing code to ensure you follow development best practices during development and implementation.
1