brainstorming

# brainstorming ## Structured-artifact boundary For new full-lane work or an existing HTML spec/plan, load [includes/artifacts.md](../../includes/artifacts.md) before artifact I/O. Before Phase 1, call `_select_authoring_route` with the trusted project root, slug, invoking workflow, and selected lane; use only its returned mode, format, and paths. For a selected HTML route it checks the installed capability before writing; missing or invalid HTML capability is a STOP and the workflow must not fall back to Markdown. Its typed ID, binding, readiness, receipt, contextual-read and scope-state rules replace legacy Markdown parsing and direct status-cell edits for that pipeline. Keep all other workflow gates, including human checkpoints, unchanged. Existing `.md` artifacts remain on their legacy path. New full-lane specs use the installed structured-artifact engine and default to canonical `.html`. HTML `--farm` dispatch remains blocked. Refine the idea before it touches code. Routed to by `/feature` and `/sprint` as their specification step. ## Caller scope and authority Read the active caller's workflow, selected lane, scope and existing delegation before refining. Initial sprint planning is not an approved sprint: this skill does not grant its own delegation. A full-lane feature requires `writing-plans` after spec approval. Initial HTML sprint planning instead returns a ready draft identity for the combined spec/plan review before either is approved; a subordinate specific...