Convert operator intent into a concrete Brief artifact via interactive dialogue.
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill brief-space-dinosaurs
Please help me install this Agent Skill. Skill: brief Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/brief Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill brief-space-dinosaurs
Interactive planning requires translating operator intent into a concrete, Skeptic-eligible Brief before architects and engineers are engaged. This Skill ensures early alignment, guards against scope ambiguity, and creates a reusable artifact for downstream planning.
Typical use cases include initiating new features from vague ideas, capturing requirements into a formal Brief, and producing a ready-to-review artifact for engineering teams.
Start a planning session by sending /brief <topic> to begin creating a Skeptic-eligible Brief.
High-intent search queries and answers about installing and using this skill.
Interactive planning translates vague ideas into actionable briefs through structured multi-turn dialogue. It guides operators by handling gray areas, capturing requirements, and generating a concrete planning artifact for downstream engineering teams.
Creating a formal planning artifact involves running an interactive dialogue that captures operator intent and resolves scope ambiguity. This process ensures early alignment and produces a reusable document ready for architectural review and execution.
Start a planning session by issuing a command with your topic to initiate the dialogue. The system persists the session state and outputs a ready-to-edit markdown draft at a designated planning path for immediate review.
Interactive dialogue handles scope ambiguity in product workflows by guiding multi-turn conversations around gray areas. It persists session state continuously, ensuring all open questions are resolved before finalizing the planning document.
The planning artifact integrates with downstream flows by pre-populating a brief path in the execution contract. This enables seamless hand-off to architect and Skeptic components, governing verification and resolving open questions.
A formal brief artifact is needed when initiating new features from vague ideas to ensure early alignment. It guards against scope ambiguity and provides a structured, reviewable document before architects and engineers are engaged.
jasonku09Interview users to define project scope, MVP, and core components.
totvsExecute implementation plans in batches with verification and review checkpoints.
calebaeroGenerates five planning artifacts from a validated site brief.
GenerativeAgentsExtract and consolidate project terms into a standardized glossary at docs/glossary.md.
