Skip to content

Ideation: date the start of spec authoring with started: (#161) - #162

Merged
clabonte merged 1 commit into
mainfrom
idea-dossier-started
Oct 15, 2026
Merged

clabonte merged 1 commit into
mainfrom
idea-dossier-started

Conversation

@clabonte

Copy link
Copy Markdown
Collaborator

Closes #161.

Changes

  • templates/initiative-idea-dossier.template.md: adds started: null, set in the same edit as graduated_to (YYYY-MM-DD). If a feature is abandoned and another started, graduated_to is repointed and the first started is kept, as Idea dossier: record when work starts with a started: date set alongside graduated_to #161 proposes. The comment says what that means for the metric: start-to-specified includes the abandoned attempts.
  • ideation-shape: records graduated_to and started together when the feature is cut.
  • ideation-groom (v0.2):
    • New start-undated class: graduated_to set and started missing or null. Report only, because groom writes only the backlog index. It never guesses a date and leaves it null where no record exists.
    • ready-to-mint now means specified, or ready with no graduated_to (the dossier-only path in initiative-intake). Before, it counted a ready idea whose specs a feature was still authoring.
    • The version note's class count is corrected: it said seven, and the table has eleven.
  • initiative-backlog.template.md: one clause mentions started.

Where this departs from #161

  • No "skill that sets graduated_to" exists. The feature is cut in the orchestrator's loop, and ideation-shape only tells the human to record it. The instruction to set started therefore goes there, and groom catches a missing one.
  • backlog-groom is ideation-groom.
  • No backfill tooling. Reading .specfuse/features/<FEAT>/events.jsonl would tie the authoring plane to the orchestrator's file layout. Nothing in this repo reads it today. Groom's start-undated report is the backfill prompt, and a human fills in the date from wherever their loop records it.

Docs and skills only. No generator or lint change.

🤖 Generated with Claude Code

The dossier recorded that a feature took an idea into authoring
(`graduated_to`) but not when, so nothing could measure ready-to-start
or start-to-specified.

- Dossier template: `started: YYYY-MM-DD`, set in the same edit as
  `graduated_to`; a restart repoints `graduated_to` and keeps the first
  date.
- ideation-shape: record both together when the feature is cut.
- ideation-groom: new `start-undated` class (report only; never guess a
  date). `ready-to-mint` now means `specified`, or `ready` with no
  `graduated_to` (the dossier-only path): a `ready` idea whose specs a
  feature is still authoring is not ready to mint.

No backfill tooling: the start date lives in the orchestrator's loop
records, which the authoring plane does not read. Groom reports the gap
and a human fills it.

Closes #161.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@clabonte
clabonte merged commit 9701c2d into main Oct 15, 2026
9 checks passed
@clabonte
clabonte deleted the idea-dossier-started branch October 15, 2026 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Idea dossier: record when work starts with a started: date set alongside graduated_to

1 participant