Plan Issue — Rich Planning Document

imboard-ai/git/plan-issue v1.9.0 risk: medium signed Stable

Read a GitHub issue and its comments, explore the codebase, confirm new states/flows are reachable, and write a rich planning document — consuming an existing plan:v1 artifact when present (validate-then-refine, never recreate) and posting the result back as the issue's canonical artifact

Use it

Inspect metadata

ai-dossier info imboard-ai/git/plan-issue

Download to the current directory

ai-dossier pull imboard-ai/git/plan-issue

Verify, then run

ai-dossier run imboard-ai/git/plan-issue

Needs the CLI.

Trust and risk

Declared risk level	medium (modifies_files, network_access)
Requires approval	no
Checksum	`sha256:b57295136deb8546e1ee4b364b6e6a223504035b0db18ea4d0dd06c3ffde79cf`
Signature	ed25519, key `imboard-ai` by Yuval Dimnik <yuval.dimnik@gmail.com>
Signed at	2026-10-14T12:23:23.140Z
Signature scheme	v3 (covers `spec-frontmatter+body`)
Public key	`m97FPrnq/zKlQArLvJl3bTZCUMWWpp/d0UJ/OfUKZeE=`

These values are copied from the published dossier header. This site does not verify them: run ai-dossier verify before trusting a dossier.

Details

Categories	development
Tags	issue, workflow, git, github, plan, planning
Authors	Yuval Dimnik
Header layout	Agent Skills spec shape
Source	raw `.ds.md`