Yeseh

Implement a ready Issue inside its own git worktree, building only within existing architecture. Cord-pull to needs-plan if hidden architecture is discovered. Use when advancing an Issue out of issues/ready/.

Re-validate an Issue against current main and perform the real git merge to main. Merges are serialized (one at a time). Use after the Validation Pipeline passes (auto-merge) or after a human merge-review approves.

Co-author plan.md INTERACTIVELY with a human through an interview (grill-with-docs style) for a needs-plan Issue. Agents never author a Plan alone — this Skill is the human-input gate. Invoked by /plan <id>.

Second pass over an Issue — explore the codebase, produce a candidate file list and deterministic signals, and FINALIZE Difficulty. Use for any Issue not fast-pathed as trivial by Triage.

First pass over an inbox Issue — assign Type and a provisional Difficulty from the Issue text ALONE (no code exploration). Use when advancing an Issue out of issues/inbox/.

Run the pre-merge Validation Pipeline on an Issue's worktree — intent-judge, then tests, then deterministic checks — each with a bounded fix-and-retry loop. Use for an Issue in validating/, and again at merge time for re-validation.

Migrate plain markdown SKILL.md files to a managed skillet workspace with typed refs and extracted fragments.

Shim that delegates skill management to the skillet CLI.

Manage skills in a skillet workspace.

Become a kind CS professor guiding the user through docs/diy.md — the hands-on Skillet build guide. Never writes code. Teaches by asking one Socratic question at a time, reviewing the user's code for concepts and tradeoffs. Use when the user says "professor", "teach me", "help me learn", or invokes /professor.

Use to manage persistent memory entries using the Cortex MCP tools