discuss

Collect user decisions to generate structured CONTEXT.md files for downstream agents.

17|3|Updated Jan 23, 2026

Search Tags:#context-management #decision-capture #context-generation #discuss #gray-area #downstream-agents

Ready to run

npx skills add https://github.com/insightflo/claude-impl-tools --skill discuss-insightflo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discuss
Source: https://github.com/insightflo/claude-impl-tools/tree/main/plugin/skills/discuss
Command: npx skills add https://github.com/insightflo/claude-impl-tools --skill discuss-insightflo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gray area 식별 및 사용자 결정 수집. CONTEXT.md를 생성하여 downstream 에이전트가 재질문 없이 작업 가능. GSD discuss-phase 패턴 기반.

Core Features & Use Cases

작업 범위 및 gray area를 식별하고 결정 수집을 자동화합니다.
CONTEXT.md 및 task별 컨텍스트 파일 생성을 통해 재질문 없이 작업 진행을 지원합니다.
실행 흐름은 Step 1~Step 5를 따라 결정 수집과 CONTEXT.md 생성을 일관되게 수행합니다.

Quick Start

Identify the current task in TASKS.md, pinpoint gray areas, collect decisions via AskUserQuestion prompts, and generate .claude/CONTEXT.md or .claude/context/{task-id}.md to enable downstream agents to work without re-asking.

Frequently Asked Questions about discuss

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I capture user decisions for gray-area tasks to generate context for AI agents?▼

To capture user decisions for gray-area tasks, this Skill identifies scoping ambiguacies across UI, API, and data tasks, then uses AskUserQuestion prompts to collect your choices and generate a structured CONTEXT.md file.

What is the best way to stop downstream agents from re-asking the same scoping questions?▼

The best way to stop downstream agents from re-asking questions is to seed a structured CONTEXT.md file with your captured decisions, enabling consistent execution without re-asking.

How do I structure context files for task-specific agent workflows?▼

You structure context files by generating a global `.claude/CONTEXT.md` or a task-specific `.claude/context/{task-id}.md` file, ensuring downstream agents can retrieve the exact gray-area decisions needed for that workflow.

Do I need a TASKS.md file to identify gray areas for context generation?▼

Yes, you need a TASKS.md file to identify the current task, which allows the Skill to pinpoint gray areas, collect decisions via prompts, and generate the corresponding context files.

Can I automate context management for multiple concurrent agent tasks?▼

Yes, you can automate context management by generating individual `.claude/context/{task-id}.md` files for each task, allowing multiple downstream agents to work concurrently with isolated, captured decisions.

What are the limitations of using CONTEXT.md for context generation across different task types?▼

The limitation of using CONTEXT.md is that it primarily targets gray-area scoping across UI, API, and data tasks, meaning highly deterministic workflows may not benefit from the decision-capture process.