How does auto-mode work in the discuss skill?

When the --auto flag is used, the skill batches all identified gray areas and questions into a single presentation rather than asking them one by one, reducing interaction overhead.

What is the difference between phase mode and project mode?

Phase mode focuses on the specific goals of a single roadmap item, while project mode (--project) handles cross-cutting decisions like tech stacks, infrastructure, and deployment strategies.

What is the primary purpose of the pbr:discuss skill?

It is used to talk through a development phase before planning begins, identifying ambiguous requirements and locking in user decisions so the AI doesn't make incorrect assumptions later.

Can the AI planner override decisions made during a discussion?

No. Decisions made during the discuss phase are considered locked. The planner must implement the user's choice exactly, even if it suggests a different approach during research.

Where are the results of the discussion stored?

Phase decisions are stored in a CONTEXT.md file within the specific phase directory, while project-level decisions are stored in .planning/PROJECT.md.

Phase Discussion & Decision Locking

Name: Phase Discussion & Decision Locking
Author: SienkLogic

bySienkLogic

•

생산성 및 워크플로

Facilitates structured pre-planning dialogues to identify project gray areas and lock architectural decisions before implementation.

The discuss skill is a critical component of the Plan-Build-Run (PBR) framework, designed to eliminate AI assumptions during the development process. By acting as a bridge between the high-level roadmap and concrete action plans, it identifies 'gray areas' where multiple technical or design paths exist. The skill prompts users for specific preferences on architecture, tech stacks, and constraints, then 'locks' these decisions into a context file. This ensures that the subsequent planning and building phases strictly adhere to the user's vision without retroactive changes or AI-driven overrides.

주요 기능

01Integrates with existing roadmaps and requirements to ensure context-aware probing.

02Identifies architectural and design 'gray areas' with trade-off analysis.

03Locks user decisions in CONTEXT.md to prevent AI overrides during planning.

04Supports both granular phase-level discussions and cross-cutting project-level context.

0511 GitHub stars

06Includes an '--auto' mode for efficient batching of discovery questions.

사용 사례

01Resolving ambiguous UI/UX requirements before starting a frontend implementation phase.

02Evaluating technical trade-offs for complex backend features to ensure architectural alignment.

03Establishing global project constraints like security posture, hosting, and data strategy.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add sienklogic/plan-build-run discuss

For use in Claude.ai and ChatGPT

Download Skill