design-session

Scope vague ideas into epics, investigations, or decisions with verification specs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dylan-conlin/orch-go --skill design-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-session
Source: https://github.com/dylan-conlin/orch-go/tree/main/skills/src/worker/design-session
Command: npx skills add https://github.com/dylan-conlin/orch-go --skill design-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires worker-base, decision-navigation.

What problem does it solve?

Transform vague ideas into concrete, actionable work artifacts through autonomous context gathering and interactive scoping.

Core Features & Use Cases

  • Autonomous Context Gathering: collects relevant kb context, decisions, and issues to anchor scoping.
  • Interactive Scope Discussion: navigates forks (boundary, priority, constraint, dependency, and NFR) to reach a decision.
  • Output Tailoring & Verification: emits an epic with children, an investigation, or a decision, plus optional verification specs for multi-agent handoffs.
  • Beads-ready Workflow: integrates with existing beads tooling for tasks, dependencies, and labels.

Quick Start

Provide a vague scope and let this skill autonomously gather context, discuss the scope, and produce an artifact (epic, investigation, or decision) based on clarity.

Frequently Asked Questions about design-session

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

FAQPage Schema
How do I turn a vague project idea into an actionable epic?

Scoping vague ideas involves navigating boundary, priority, constraint, dependency, and NFR forks to reach a decision, ensuring the resulting work artifact is concrete and actionable.

What is interactive scoping for project planning?

Interactive scoping for project planning uses autonomous context gathering to navigate boundary, priority, and NFR forks, producing tailored work artifacts like investigations or epics.

How do I scope work artifacts when requirements clarity is uncertain?

Scoping work artifacts with uncertain clarity adapts the output based on the idea's definition level, emitting an Epic with children, an Investigation, or a Decision accordingly.

Does this scoping workflow require the decision-navigation dependency?

Yes, this scoping workflow requires the decision-navigation and worker-base dependencies to guide explicit scoping forks and ensure traceability during interactive context gathering.

Can I generate verification specifications for multi-agent handoffs?

Yes, you can generate optional verification specifications for multi-agent handoffs to ensure quality and traceability when outputting an Epic, Investigation, or Decision artifact.

How do I integrate scoped epics with Beads workflow tooling?

Integrating scoped epics with Beads workflow tooling works by mapping the produced artifacts to existing beads tooling for tasks, dependencies, and labels to ensure traceability.