OpenParable
Skip to content
← Back to skills

Kata Discuss Phase

Productivity
kata-discuss-phase

Kata Discuss Phase is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Gather phase context through adaptive questioning before planning, clarifying implementation decisions, or exploring gray areas for a phase. Triggers include "discuss phase", "clarify phase", "gather context", "what are the gray areas", and "phase discussion".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/planning/kata-discuss-phase/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/kata-discuss-phase, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

How it works:

  1. Analyze the phase to identify gray areas (UI, UX, behavior, etc.)
  2. Present gray areas — user selects which to discuss
  3. Deep-dive each selected area until satisfied
  4. Create CONTEXT.md with decisions that guide research and planning

Output: {phase}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again

<execution_context> @./references/phase-discuss.md @./references/context-template.md </execution_context>

Load project state: @.planning/STATE.md

Load roadmap: @.planning/ROADMAP.md

CRITICAL: Scope guardrail

  • Phase boundary from ROADMAP.md is FIXED
  • Discussion clarifies HOW to implement, not WHETHER to add more
  • If user suggests new capabilities: "That's its own phase. I'll note it for later."
  • Capture deferred ideas — don't lose them, don't act on them

Domain-aware gray areas: Gray areas depend on what's being built. Analyze the phase goal:

  • Something users SEE → layout, density, interactions, states
  • Something users CALL → responses, errors, auth, versioning
  • Something users RUN → output format, flags, modes, error handling
  • Something users READ → structure, tone, depth, flow
  • Something being ORGANIZED → criteria, grouping, naming, exceptions

Generate 3-4 phase-specific gray areas, not generic categories.

Probing depth:

  • Ask 4 questions per area before checking
  • "More questions about [area], or move to next?"
  • If more → ask 4 more, check again
  • After all areas → "Ready to create context?"

Do NOT ask about (Claude handles these):

  • Technical implementation
  • Architecture choices
  • Performance concerns
  • Scope expansion

<success_criteria>

  • Gray areas identified through intelligent analysis
  • User chose which areas to discuss
  • Each selected area explored until satisfied
  • Scope creep redirected to deferred ideas
  • CONTEXT.md captures decisions, not vague vision
  • User knows next steps </success_criteria>