Create a feature Issue from a roadmap block

[taspinar]

What changed

• ./scripts/create-feature-issue.sh <feature-id> (for example F03) finds the roadmap heading that starts with the ID and uses everything up to the next heading of the same or a higher level as the Issue body, unchanged, with a reference to docs/roadmap.md. Lines inside fenced code are not treated as headings.
• The heading becomes the title, so the feature ID is visible and triage-review.sh can use it for follow-up provenance.
• The proposed Issue is shown and created only after approval.
• It refuses an unknown or duplicated feature ID, an empty block, and a second Issue for a feature that already has one, open or closed. A failing lookup of existing Issues stops the run.
• It warns when the block refers to another feature whose Issue is still open, or whose status could not be checked.
• No agent is involved. The title-and-file form remains for Issues that are not roadmap features. The script is now executable.
• README, docs/development.md, and docs/agentic-workflow.md show the command as the step after the planning PR.

Issue / acceptance criteria

Closes #41

Risk

• Low
• Medium
• High

Verification evidence

• ./scripts/verify.sh passed (11 checks)
• Tests added/updated where appropriate (tests/create-feature-issue-test.sh, also passing under macOS system bash 3.2)
• Independent review completed when required
• Architecture/docs/ADR updated when required

Tested with a fake GitHub CLI only.

Independent review: Codex (gpt-6-astra), read-only. CHANGES REQUIRED:

• M1 (heading-like lines in fenced code truncated the block): fixed, with a test.
• MIN1 (a failing dependency lookup was ignored): fixed; a failing lookup for the feature itself stops the run, for a referenced feature it warns. Tested.

Not re-reviewed after the fixes.

Agent involvement

Planner: —
Implementer: Claude (Opus 5.5)
Reviewer: Codex (gpt-6-astra)

Production impact

None.

🤖 Generated with Claude Code