bala2006/eng-toolkit
Rigorous AI software-engineering toolkit for Kiro, adapted from the Cursor plugins pstack, thermos, continual-learning, and ralph-loop. Provides an engineering workflow router, deep independent review, persistent memory, and bounded iterative execution.
Sketch types, signatures, and module structure before writing code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping straight to code would lock in the wrong shape.
Spawn N parallel candidates at the same task, pick a base, and graft the strongest parts of the others into it. Use for /arena, 'arena this', 'throw it in the arena', competing approaches, or when one attempt at a non-trivial artifact would lock in the wrong shape.
Cancel an active bounded Ralph loop and report where it stopped. Use for /cancel-ralph, 'cancel the ralph loop', 'stop iterating', or 'abort the loop'.
Capture durable user coding preferences and project facts into AGENTS.md so future sessions reuse them. Use for /continual-learning, 'remember this', 'update AGENTS.md', 'learn my preferences', or when a recurring preference, project convention, or engineering decision is worth persisting. Incremental, idempotent, and never stores secrets.
Adversarially review code changes from multiple independent angles, then synthesize a verdict. Use for /interrogate, 'adversarial review', 'multi-model review', 'challenge this', 'stress test this code', 'find blind spots', or 'tear this apart'. Does NOT auto-apply changes.
Rigorous engineering workflow router (pstack, adapted for Kiro). Use for /poteto-mode, 'poteto mode', or any non-trivial engineering task (feature, bug fix, refactor, performance, investigation, prototype, migration, review, or work you step away from) that needs a deliberate workflow instead of jumping straight to code. Routes the task to the right playbook and skill.
Apply pstack's engineering principles to a coding decision. Use for /pstack-principles, or when you want the rigorous principle set that grounds architecture, verification, delegation, and code-quality choices. Referenced by the poteto-mode router.
Run a bounded iterative execution loop that repeatedly works, tests, and fixes a clearly-defined task until an explicit completion condition holds or a maximum iteration count is reached. Use for /ralph-loop, 'start a ralph loop', 'iterate until', 'get all tests passing', 'complete this migration', or 'keep testing and fixing until X'. Always bounded; never runs unlimited.
Explain what the bounded Ralph loop is, how it works in Kiro, when to use it, and its safety limits. Use for /ralph-loop-help, 'how does ralph loop work', or 'help with the ralph loop'.
Fan out N parallel workers, drain them, and return one consolidated report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration fan-out.
Make a bug executable with a failing regression test before changing production code. Use when the user explicitly asks for TDD, a failing test, or a regression test, OR when a bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Run a deep independent review of a branch/diff before shipping: launch a security-and-correctness pass and a maintainability pass, then synthesize their findings into one verdict. Use for /thermos, 'thermos', 'thermo nuclear review', 'deep review', 'review this branch/PR before shipping', or a combined bug/security and code-quality audit. Read-only by default; does not modify code.