ashneil12/hivra-rpi
Research, plan and build phases. The first mate runs each skill by name. They are not part of the always-on skill index.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
A relentless interview to sharpen a plan or design.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Only use when the user explicitly invokes this skill by name.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Only use when the user explicitly invokes this skill by name.