feat(skills/resuming-a-feature): add cold-resume skill and pending-snapshot convention#29
Merged
Merged
Conversation
…apshot convention
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a first-class “cold resume” entrypoint to the workflow by introducing a new router skill that treats the orchestration state file as an executable resume contract, and updates the state-file template + planning skill to establish a “Pending snapshot” convention for pause/resume continuity.
Changes:
- Introduce
feature-dev-workflow:resuming-a-featureto locate/read/verify/reconcile the state file and route work by recorded phase. - Extend the feature state template with a
## Pending snapshotsection and update the resume checklist to prefer the new skill (with a fallback). - Update
planning-a-featureStep 8 language to include the pending snapshot and the resume skill as the canonical resume path.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| skills/resuming-a-feature/SKILL.md | New resume router skill defining the trust-vs-verify protocol and phase-based routing for cold sessions. |
| skills/planning-a-feature/templates/feature-state.md | Adds ## Pending snapshot and updates resume instructions to point to the new skill. |
| skills/planning-a-feature/SKILL.md | Updates Step 8 to include pending snapshot and reference resuming skill as the resume entrypoint. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…able with placeholders git rev-parse --verify and gh pr checks were missing their required arguments; a cold session can't run them as written. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J1vgUwZZpzavETACT3fXPM
…ck resume checklist Sub-PR branches are based on the feature branch, so main..HEAD includes inherited commits; the upstream check matches what resuming-a-feature verifies. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J1vgUwZZpzavETACT3fXPM
…le and the project-CLAUDE.md ownership table A router skill nobody can discover fails its purpose; CLAUDE.md requires the discovery docs to track skill additions. The mermaid diagram is unchanged: it depicts the conception-to-ship path, which resume re-enters rather than extends. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J1vgUwZZpzavETACT3fXPM
…-branch instead of @{u}
@{u} errors on a branch with no upstream — exactly the state of an in-progress worktree that hasn't pushed yet, which a cold resume must handle.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J1vgUwZZpzavETACT3fXPM
…o it runs without an upstream Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J1vgUwZZpzavETACT3fXPM
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
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.
Problem
The state file is the resume contract, but nothing consumes it as one. A session resuming a feature past active development matches no skill's trigger (developing-a-feature is "starting implementation against a written plan"), so the user compensates with a hand-written resume prompt reconstructing what the state file already records; in a live session that prompt ran ~40 lines. A baseline cold-session agent asked to "resume the feature" needed seven tool calls and six full skill reads to derive the protocol, and correctly reported that "a stacked configuration with human staged merges is a third sub-PR model the plugin never enumerates" — it also had to lean on a wrap-up checklist the previous session had improvised into the state file, a section the template never defined. The producing side has the mirror-image gap: no convention says a pausing session must leave a cold-start-executable snapshot behind.
Change
skills/resuming-a-feature/SKILL.md: the cold-resume router. Locate the state file (state files live on feature branches, not main), read it in full, verify every mutable fact against live git/GitHub before trusting it (trust-vs-verify table; reconcile and push the file first on any divergence), treat the bubble-up log as settled adjudications, route by thestatus:frontmatter (including the previously unownedreviewphase: retargets/flips via opening-a-pull-request, checkpoints via reviewing-feature-progress, issue closure via writing-github-issues, teardown via developing-a-feature Step 7), and report the reconciled picture before any mutation. The merge guard survives the phase transition explicitly.## Pending snapshotsection, refreshed at the end of every work burst and always at a pause — the ordered next actions a cold session executes from. The template's resume checklist now points at the skill (with the manual list kept as a fallback), and planning-a-feature Step 8 names the skill as the resume path.Verification (writing-skills RED → GREEN)
Related
opening-a-pull-requestmatches retargets by trigger (gh pr edit) but has no retarget-specific guidance (confirm the base change, re-check the keyword per feat(skills/opening-a-pull-request): document keyword and linkage semantics for stacked retargeted PRs #26, CI expectations after a base change). Worth its own PR.