-
Notifications
You must be signed in to change notification settings - Fork 0
Integration OpenSpec
You're using OpenSpec (spec-driven changes tracked as proposals under a
changes/ or openspec/ directory, each with its own tasks) alongside
wiki_ticket_sdd, and want those proposals to become tracked, published
work rather than staying local-only.
Nothing to install on the wiki_ticket_sdd side — OpenSpec is set up
independently, per its own instructions.
Not applicable. OpenSpec has no ticketing/wiki adapter concept; nothing
to configure in .work/config.yml.
Treat an OpenSpec change proposal the same way as a SpecKit spec or a
hand-written design doc — it's the why, and wiki_ticket_sdd's
plan-capture is what turns its task list into tracked, published work:
- Draft and approve the OpenSpec change proposal as normal.
- Feed its task breakdown into
plan-capture(reformat to- [ ] (P#) Titleplus a one-to-three-sentence description per task if OpenSpec's own format differs). - Keep the OpenSpec proposal document itself as the permanent design
record — same role this repo gives its own
docs/plans/, so avoid re-deriving the rationale inside thewiki_ticket_sddplan body; a short pointer back to the OpenSpec proposal is enough. - Execute and close out through
wiki_ticket_sddas usual.
Each captured task becomes an ordinary create event in
.work/todo.jsonl — no OpenSpec-specific event shape.
Not applicable — nothing external to pull. If the OpenSpec proposal changes after capture, write a new plan that supersedes it rather than editing the captured one.
Identical to any other captured plan — ticket pages per work item, the frozen plan doc published to the wiki.
- OpenSpec's own "archived" state for a completed proposal and this repo's
done/cancelleditem statuses are two independent lifecycles — closing work items here doesn't archive the OpenSpec proposal, and vice versa. - As with SpecKit, don't try to keep two live task lists (OpenSpec's and
.work/todo.jsonl's) in sync by hand after capture — capture once, thenwiki_ticket_sdd's log is the one that's tracked and published.
2026-07-25 — edit this page
- Roadmap
- Design-Doc · Code-Walkthrough
- Plan: Plan-ia-content-model
- Plan: Plan-ticket-sync-and-init-detection
- ADR-0001-event-log-fold-union-merge
- ADR-0002-skill-based-edges-typed-contract
- ADR-0003-green-gates-merge
- Index-Releases
- Latest snapshot: Roadmap-2026-07-29_v0.18.0-release
- Index-Status
- Index-Decisions