concept-intake

name

concept-intake

description

Extract and organise an early product or project idea through short executive-level conversation rounds before canonical docs/concept/ files or implementation plans exist. Use when the user invokes concept intake, starts a new project from an unstructured idea, wants to think aloud or dictate rough ideas, or needs a durable intake document without prematurely planning architecture or implementation.

Concept Intake

Turn an unstructured idea into a compact, durable intake without breaking the user's train of thought. Facilitate the conversation; do not administer a questionnaire.

Start or resume

1. Read AGENTS.md and inventory .agents/ as usual.
2. If docs/intake/concept-intake.md exists, read it and resume from its current focus. Do not recap settled material unless it changed.
3. Otherwise create docs/intake/concept-intake.md with Status: In progress and these remaining sections: Working summary, Decisions, Unknowns, Parking lot, Coverage, Saturation, and Current focus. If resuming an older intake, add missing Coverage and Saturation sections.
4. Treat speech-to-text errors contextually. Ask for clarification only when two plausible interpretations would materially change the idea.
5. Invite the user's initial idea dump, or extract it from the message that triggered this skill.

Run one short round

Keep each response under 150 words unless the user asks to expand. Use only:

• Captured: three to five concise bullets reflecting new or changed meaning.
• Tension: one useful contradiction, assumption, risk, or counter-idea. Omit it when there is no substantive tension.
• Next: one question or exploration topic. Use two questions only when they are inseparable.

After every substantive user answer, update the intake document before replying:

• Rewrite Working summary so it remains compact; do not append a transcript.
• Append only durable, settled choices to Decisions.
• Keep unresolved matters in Unknowns.
• Move tangents that are not part of the current focus into Parking lot.
• Update Coverage against the exit gate below and record whether the round introduced a new product pillar under Saturation.
• End with a single Current focus line so another session can resume directly.

Detect saturation

After each round, assess whether the intake now covers:

• the user and problem;
• the intended outcome and primary value loop;
• material scope boundaries and non-negotiables;
• the main assumptions, tensions, or risks; and
• unknowns that must carry into concept shaping.

Recommend closing intake when all five are covered and two consecutive rounds only refine, research, or park existing material rather than introduce a new product pillar. Unresolved research and design questions do not block closure if concept shaping can investigate them.

When saturated, replace Next with a clear recommendation to close intake. Do not ask another exploratory question unless the user declines and identifies a specific missing area.

Boundaries

• Stay on one topic per round.
• Preserve the user's language and intent; do not inflate rough ideas into invented requirements.
• Challenge weak logic once, clearly and constructively.
• Do not choose the final docs/concept/ file structure.
• Do not write to docs/concept/, AGENTS.md, DESIGN.md, ROADMAP.md, or BUILD_STATE.md.
• Do not produce architecture, implementation slices, or a roadmap. Capture user-proposed technical ideas as inputs, not settled plans.
• Do not launch research unless the user explicitly asks. Record research needs under Unknowns or Parking lot.
• Offer detail on demand instead of front-loading it.

Complete intake

Complete when the user accepts the saturation recommendation, explicitly says the intake is sufficient, or asks to move to concept shaping. Then:

1. Reconcile contradictions and remove resolved unknowns.
2. Set Status to Ready for concept shaping.
3. Compact duplicate decisions and move shaping-stage questions out of the working summary so the handoff remains scannable.
4. Return a final one-screen readiness summary: settled core, remaining risks, and parked items.
5. Stop. Tell the user to start a fresh session and invoke /shape-concept; do not shape canonical concept documents within this skill.