gannonh/kata-skills

kata-list-phase-assumptions

Surface Claude's assumptions about a phase approach before planning, checking what Claude thinks, or validating understanding before planning. Triggers include "list assumptions", "what are you thinking", "show assumptions", "phase assumptions", and "what's the plan".

First seen Feb 6, 2026

Installation

$ npx skills add gannonh/kata-skills --skill kata-list-phase-assumptions

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from gannonh/kata-skills · top by installs.

npx skills add gannonh/kata-skills

Browse all from gannonh/kata-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.6.1
More metadata
version
1.6.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,602 B
  • docs SUMMARY.md 303 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 21 installs

SKILL.md

<objective> Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.

Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt </objective>

<executioncontext> @./references/phase-assumptions.md </executioncontext>

<context> Phase number: $ARGUMENTS (required)

Load project state first: @.planning/STATE.md

Load roadmap: @.planning/ROADMAP.md </context>

<process>

  1. Validate phase number argument (error if missing or invalid)
  2. Check if phase exists in roadmap
  3. Follow phase-assumptions.md workflow:

- Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?"

  1. Gather feedback and offer next steps

</process>

<success_criteria>

  • Phase validated against roadmap
  • Assumptions surfaced across five areas
  • User prompted for feedback
  • User knows next steps (discuss context, plan phase, or correct assumptions)

</success_criteria>