Loading...
Loading...
Found 15 Skills
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
Gemini CLI consultation workflow for coding agents. Use when technical tasks need Gemini consultation for decisions, planning, debugging, problem-solving, or pre-implementation guidance.
ALWAYS invoke this skill at the START of every session before doing any other work. This skill ensures the host project has agent governance rules (skill routing, pre-implementation protocol, issue tracking conventions) installed in its context file. It is idempotent — if rules are already present, it exits silently. Without this skill running first, other swain skills (swain-design, swain-do, swain-release) will not be routable.
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
Build a pre-implementation harness for ambiguous or risky coding tasks by grounding the request in the repository, producing a structured impact map, surfacing ambiguities and risks, defining scope boundaries, and creating a validation-ready implementation contract before any code changes are made. Use when a task is broad, underspecified, cross-cutting, or likely to drift without an explicit planning checkpoint.
Groom and route tickets on ANY project board through a shared status vocabulary (from raw `Triage` to a fully spec'd `Ready for Agent` or `Ready for Human`) so engineer only ever executes work that is already specified. Tracker-agnostic (GitHub Projects, Linear, or any board via a small adapter). Use to create/triage/groom issues, prepare work for an AFK agent, or manage the pre-implementation flow. Pairs with engineer + reviewer.
Capture current page layout, styles, and structure from a live web page using Chrome DevTools MCP. Use when you need to understand the existing UI before making changes — captures screenshots, DOM structure, computed styles, and layout properties. Useful as a pre-implementation baseline for frontend or UI-affecting changes.
Transform project briefs into testable specifications with acceptance criteria. Use for requirements translation, spec creation, pre-implementation. Skip if spec exists or still exploring.
Use when planning new features or changes to identify failure scenarios before implementation
Use when the user asks to review, confirm, walk through, or pre-check a saved Markdown implementation plan before implementation; interactively reviews plan items one at a time and manages localized item-level decisions.
Use when `spec.md`, `plan.md`, and `tasks.md` exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution conflicts before implementation.
Research a topic, technology, or approach. Use when the user needs investigation or information gathering before implementation.