Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

semi-sentient

@semi-sentient source repo

8 published skills

  1. ▌
    Grill Me · semi-sentient
    Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree and the sub-decisions it unlocks. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me", "devil's advocate", "challenge my assumptions", "poke holes in my plan", "what am I missing". Also use instead of asking ad hoc when you are about to ask the user three or more design questions, or any question whose answer would change what you ask next.
    0
    installs
  2. ▌
    Run Plan · semi-sentient bundle
    Execute a multi-phase implementation plan by delegating each phase to sub-agents with fresh context windows. Use when the user invokes run-plan with a plan file path, GitHub issue number (e.g. `#456`), or full issue URL.
    0
    installs
  3. ▌
    Prd To Plan · semi-sentient bundle
    Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file and optionally published as a GitHub sub-issue. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets". Accepts an optional GitHub issue reference (e.g. `#123` or a full issue URL) to link the plan as a sub-issue of that PRD-epic.
    0
    installs
  4. ▌
    Write A Prd · semi-sentient
    Create a PRD through user interview, codebase exploration, and module design, saved as a local Markdown file and optionally published as a GitHub issue with the `epic` label. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. Pass `--no-github` to skip the publish prompt.
    0
    installs
  5. ▌
    Grill With Docs · semi-sentient bundle
    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions. Also use instead of asking ad hoc when you are about to ask the user three or more design questions, or any question whose answer would change what you ask next; prefer this skill over grill-me when the repo has a CONTEXT.md or ADRs.
    0
    installs
  6. ▌
    Tend Steering Docs · semi-sentient bundle
    Condense or split a repo's agent steering docs (AGENTS.md, CLAUDE.md, docs/agents/*) without losing load-bearing rules; surfaces contradictions between rules and produces a human-reviewed Removal Ledger before any deletion. Use to clean up, tighten, split, or de-conflict bloated or stale agent docs.
    0
    installs
  7. ▌
    Tdd · semi-sentient bundle
    Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
    0
    installs
  8. ▌
    Commit · semi-sentient
    Generate a commit message from staged changes and commit. Accepts an optional ticket identifier argument; when omitted, infers an issue reference from the branch name or conversation (`--no-ticket` suppresses inference).
    0
    installs