techne

Explore intent, requirements, and design before any implementation — produces a validated spec

Execute the task breakdown from a plan.md, with TDD discipline and a spec-check gate

Write the spec-to-implement (plan.md) for a goal into .techne/tasks/<slug>/

Code review of the current branch — produces a structured review of completed work

Bootstrap .techne/ at the repo root and add it to .gitignore

Use after initial design context is gathered, before brainstorming - resolves contradictions in requirements, disambiguates terminology, clarifies scope boundaries, and verifies assumptions to prevent building the wrong solution

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches morphe:code-reviewer subagent, handles retries and timeouts, manages review-fix loop until zero issues