Repository navigation
Add /archive-spec command to close out completed specs - #21
Merged
Merged
Conversation
Cover the new /archive-spec command introduced in ferrus 0.3.1-alpha.1: - Add a "Closing out a spec" section to the Specs & Milestones guide describing the ## Outcome section, the guided supervisor flow, archival preconditions, and the machine-local archive layout. - Add /archive-spec to the HQ command cheat sheet and note that /spec now offers to archive a completed selected spec first. - List archive_spec under the supervisor's definition-session tools. - Document the archive/specs/<spec-slug>-<closed-at>/ directory in the runtime files tables. - Mention spec archival in the quickstart. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XM86vDED2LvTfoXgNnVk9g
RomanEmreis
force-pushed
the
claude/ferrus-docs-archive-spec-aprz0j
branch
from
July 10, 2026 09:45
276e44e to
2f68394
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces the
/archive-speccommand, which allows users to formally close out a completed specification by generating an## Outcomesummary and archiving its associated task and run artifacts into machine-local storage.Key Changes
New
/archive-speccommand: Guides users through archiving a completed spec with supervisor assistance## Outcomesection capturing what shipped, deviations from plan, validation evidence, and follow-up work## Outcomesection in the spec file itself.ferrus/tasks/<task-id>.md) and run artifacts (.ferrus/runs/<task-id>/) to machine-local archive under~/.ferrus/projects/<project-id>/archive/specs/Preconditions enforcement:
/archive-specvalidates that:Archive structure: Organized under machine-local project directory with
manifest.toml, spec copy, and relocated task/run artifactsIntegration with
/spec: When starting/specwith an already-completed spec selected, ferrus now offers to archive it first before drafting a new specificationDocumentation updates:
archive_spectool to supervisor role in agents documentationImplementation Details
.ferrus/tasks/and.ferrus/runs/focused on active work## Outcomesectionferrus.dbfor queryabilityferrus doctorcontinues to account for relocated run artifacts## Outcomesections serve as compact project memory for future agent sessionshttps://claude.ai/code/session_01XM86vDED2LvTfoXgNnVk9g