Description
Capture to Dots is the fast path from something noticed in conversation to a durable, correctly shaped record. It recognizes bugs, ideas, Projects, Tasks, lessons, notes, workflow optimizations, roadmap items, and store-specific rows, then routes each kind to the appropriate Dotabase and template. The goal is to preserve useful work without forcing a full planning ceremony.
The feature resolves scope and required relationships before writing, uses deterministic row helpers, and returns the created handle so later workflows can refer to a real record. It also keeps meaningful boundaries: a product dream can be captured without replacing the Idea Stage, and a small observation can be saved without inventing a Project.
Selling Points
- Prevents valuable decisions and defects from disappearing in transient conversation.
- Routes each captured item to the store and shape people expect, reducing cleanup and duplicate records.
- Returns a durable handle immediately, so teams can link, prioritize, or investigate later.
- Supports lightweight capture without dragging the buyer through unnecessary delivery ceremony.
- Shares one workflow across Dots and IAGREED, keeping platform records and agent actions aligned.
User Story
During a build review, a developer notices an unrelated accessibility bug that should not derail the current Task. They ask to capture it. The feature resolves the product scope, writes a structured bug row with the evidence already available, and returns its handle. The current work continues, while the defect is safely available for triage and remediation.
Extension Surface
This shared platform-face feature is automatable. payload/skills/capture/SKILL.md exposes the routing behavior, and payload/skills/capture/scripts/capture-row.mjs drives deterministic creation through the Dots CLI. The specialized workflows under payload/skills/capture/workflows/ make supported record types explicit. Consumers can invoke the whole flow, but cannot register arbitrary capture types without changing the shipped payload and platform schema.
Capabilities & Limits
- Captures multiple durable record types with type-appropriate fields, templates, and scope relations.
- Resolves Project or Task references before writing and returns the actual created handle.
- Separates lightweight capture from stage workflows that require deeper conversation or validation.
- Limit: it does not plan, audit, prioritize, or remediate the captured item, and it cannot invent missing schema options.
Implementation Map
payload/skills/capture/SKILL.mdpayload/skills/capture/workflows/capture-store-row.mdpayload/skills/capture/workflows/capture-bug.mdpayload/skills/capture/scripts/capture-row.mjs