Open Thread

Turn a user's starting point into a durable thread on disk. You interpret the raw input, compose the seed's fields, and create the thread — in one pass, without stopping to confirm anything.

Inputs

Gather the following before composing any field; the composition below works from what you gather here.

• The project's AGENTS.md, when the file exists — the project's standing guidance for agents working in it.
• docs/glossary.md, when the file exists — the project's fixed terms, to be used in everything you write.
• docs/adr/ and docs/pdr/, read via /consult-decisions — the project decisions bearing on the starting point.
• The roadmap index under .work/roadmaps/, when supplied — a project-level file for composing the seed. Find the entry in it as a heading whose text is the supplied slug, in the shape <skill_path>/references/formats/roadmap-index.md defines, and read that entry's sketch and scope boundary. When the index carries no heading with that slug, create nothing: tell the user the slug is absent and name the slugs the index does carry, so they can correct the invocation.
• The ticket, when supplied — material for composing the seed; read it as <skill_path>/references/supplied-ticket.md directs.

The starting point itself comes with the invocation, in any combination of three forms, at least one of which is present:

• A rough idea in prose, describing what the work is.
• An external ticket reference — a tracker URL or identifier.
• A roadmap entry — an index path under .work/roadmaps/ together with the entry's slug.