analysis-process
Task Analysis Process
Goal: Before writing any code, make sure you understand the requirements and have an implementation plan ready.
Ideas and Prototypes
Use this for ideas that are not fully thought out and do not have a fully-formed design/specification and/or implementation-plan.
For example: I've got an idea I want to talk through with you before we proceed with the implementation.
Your job: Help me turn it into a fully formed design, spec, implementation plan, and task list.
See idea-process.md.
Continue WIP Feature
Use this to resume work on a feature that already has design docs and a task list in /docs/wip/.
For example: Let's continue working on the auth system.
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.
1merge-docs
Semantically compare and merge two design docs for the same feature into one unified document. Use when you have two competing or complementary design/implementation docs (e.g., from separate analysis-process runs) and need to reconcile them into a single source of truth.
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