Orchestrator/bahn/teamlandkarte-mcp/.github/prompts/openspec-archive.prompt.md at 2e35796f37348c6eb51c77475b59a383da947ab2

Files

T

ankn a5f8fb49ab Migrate all repos into monorepo context folders

Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
      Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
      Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)

Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.

2026-06-30 20:39:52 +02:00

1.9 KiB

Raw Blame History

description

description
Archive a deployed OpenSpec change and update specs.

$ARGUMENTS

Guardrails

Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
Keep changes tightly scoped to the requested outcome.
Refer to openspec/AGENTS.md (located inside the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.

Steps

Determine the change ID to archive:
- If this prompt already includes a specific change ID (for example inside a <ChangeId> block populated by slash-command arguments), use that value after trimming whitespace.
- If the conversation references a change loosely (for example by title or summary), run openspec list to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
- Otherwise, review the conversation, run openspec list, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
- If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
Validate the change ID by running openspec list (or openspec show <id>) and stop if the change is missing, already archived, or otherwise not ready to archive.
Run openspec archive <id> --yes so the CLI moves the change and applies spec updates without prompts (use --skip-specs only for tooling-only work).
Review the command output to confirm the target specs were updated and the change landed in changes/archive/.
Validate with openspec validate --strict and inspect with openspec show <id> if anything looks off.

Reference

Use openspec list to confirm change IDs before archiving.
Inspect refreshed specs with openspec list --specs and address any validation issues before handing off.

1.9 KiB Raw Blame History

1.9 KiB

Raw Blame History