ooshka
- 5 skills
- 0 followers
- 10 hours ago last updated
- ▌ Planner · ooshka bundleDevelopment planner for deciding the next concrete implementation step, balancing feature delivery with hardening, spotting tech debt/refactor signals, and producing small agent-ready Case files under agent_docs/. Use only when the user explicitly asks for `$planner`, explicitly asks to use the planner skill by name, or explicitly asks for planner-driven Case generation in this workflow. Do not use for generic planning questions unless the user specifically invokes this skill.
- ▌ Worktree · ooshka bundleSpin up an isolated, sandboxed git worktree for a long-running/autonomous agent. Creates the worktree in a central tree (~/projects/worktrees/<repo>/<name>, never under a repo's .claude/) and seeds it with a .claude/settings.local.json that enables the OS sandbox so bash + git run hands-off, confined to the worktree. Use when the user wants to "spin up a worktree for an agent", run unattended/long-running work, or avoid babysitting bash permission prompts.
- ▌ Reviewer · ooshka bundleCollaboratively review code quality with a mentoring posture, focused on architecture, design patterns, language idioms, code smells, and tech debt. Use only when the user explicitly asks for `$reviewer`, explicitly asks to use the reviewer skill by name, or explicitly asks for this skill's post-implementor review workflow. Do not use for ordinary review or design-advice requests unless the user specifically invokes this skill.
- ▌ Implementor · ooshka bundleImplement code changes from planner-generated Case files under agent_docs/cases/. Use only when the user explicitly asks for `$implementor`, explicitly asks to use the implementor skill by name, or explicitly asks to execute an existing planner/reviewer Case with this skill. Do not use for ordinary coding requests unless the user specifically invokes this skill.
- ▌ Slice Runner · ooshka bundleEnd-to-end roadmap slice execution for personal repos. Use when the user explicitly asks for `$slice-runner`, asks to run a slice from planner through implementor/reviewer/CI/merge, asks to take the next roadmap or backlog item end-to-end with minimal human interaction, or asks for autonomous Case execution including branch creation, implementation, verification, CI, review hygiene, merge, and push.