taches-principled

Create a handoff document for continuing work in a fresh session

Apply systematic debugging methodology to investigate issues deeply

Simplify and refine recently modified code for clarity and maintainability

Synthesizes multiple evaluation results into an actionable improvement plan. Use after grading and comparing skills to generate prioritized recommendations.

Reviews code for quality, security, and best practices. Invoke when user asks for code review, PR review, or code quality feedback.

Compares two skill versions to identify what changed and why it matters. Use when a skill was revised and you want to understand the delta.

Scores skill outputs against teaching-focused rubrics. Use when evaluating whether a skill teaches judgment or just prescribes steps.

Expert prompt engineer for Claude Code. Use when creating, optimizing, or executing reusable prompts for task automation. Invoke when user asks to 'create a prompt', 'write a prompt', 'make a prompt executable', or 'run a prompt'.

Root cause analysis methods — Five Whys for single-path causes and Fishbone for multi-category exploration. Use when debugging incidents or analyzing problems.

Traces bugs backward through the call stack to find the original invalid data or incorrect behavior trigger

Orchestrate general-purpose parallel subagents for investigation, self-review, and feedback loops. Use for multi-perspective research, review, and delegated exploration — NOT for executing structured task plans (use a plan-execution workflow instead).

Update project documentation for code changes using multi-agent workflow with specialized tech-writer agents. Covers READMEs, guides, API docs, and JSDoc.

Apply Strunk & White's Elements of Style to make documentation clearer, stronger, and more professional. Active voice, positive form, concrete language, omit needless words.