kaisa-kucherenko
- 6 skills
- 0 followers
- 13 hours ago last updated
- ▌ Spec · kaisa-kucherenko bundleTurns a closed ADR into a phase spec an LLM implementer executes phase by phase: cuts, orders and describes — decides nothing (the ADR did), implements nothing (the implementer agents do). Triggers: "/spec", "спека", "напиши спеку", "спека фаз", "нарізка фаз", "write the spec", "phase spec". Requires an ADR with no decision left PENDING (each DECIDED or DROPPED) and its review closed — without one, stop and point at /adr. Running the phases (briefing, gate, review, commit) is /implement, not this skill.
- ▌ Twix · kaisa-kucherenkoTwo-reviewer pass on the current diff, then one merged verdict — the house rules for every review panel live here. Presets: "твікс" / "/twix" = Agatha (deep Claude) + Arthur (Codex); "твікс лайт" / "twix light" = Arthur + Dash (fast, no Opus). Names in the trigger override the preset ("твікс Агата і Деш"). For the full three-reviewer panel with synthesis use the precogs workflow — it follows the panel rules below.
- ▌ Pickup · kaisa-kucherenkoStart a fresh session from a handoff file written by /handoff — find it, read it, verify it against current reality, and begin the NEXT step. Triggers: "/pickup", "pick up the handoff", "continue from the handoff", "підхопи хендоф", "продовжуй з хендофу" (add triggers in your own language), or a session opening with an @-mentioned HANDOFF file. Counterpart of /handoff.
- ▌ Handoff · kaisa-kucherenkoCreate or update a session handoff file so a fresh session continues seamlessly where this one stopped. Triggers: "/handoff", "make a handoff", "update the handoff", "add to the handoff", "is the handoff current?", "зроби хендоф", "онови хендоф", "запиши в хендоф" (add triggers in your own language). Create ONLY on explicit request (never unprompted); once the file exists, keep it current through the session. Universal across projects. Counterpart: /pickup reads the file in the new session.
- ▌ Implement · kaisa-kucherenkoRuns ONE phase of a phase spec (written by /spec) through the full cycle: find the next phase from the live handoff, brief the user first, launch the implementer, freeze the tree, gate the diff against the phase's Acceptance, external review of the user's choice, local testing, commit, mark done, update the handoff. Triggers: "/implement" (next phase from the handoff), "/implement N", "фаза N", "запускай фазу", "роби фазу", "наступна фаза", "run phase N". Needs a spec with a phase map; without one, stop and point at /spec.
- ▌ Adr · kaisa-kucherenkoArchitecture Decision Record — structured approach to making architectural decisions for complex features. Use when: user needs to design a new feature that touches multiple layers (DB, API, frontend, security), user says '/adr', 'architectural decisions', 'decision tree', 'архітектурні рішення', 'давай продумаємо архітектуру', 'треба прийняти рішення по архітектурі', or when a feature is too complex to just start coding. Also trigger when user has a GitHub issue for a feature and wants to plan implementation before writing code. This skill is about DECISIONS, not implementation — it produces a decisions document that serves as the spec.