Every Story Should Be Resumable

Make one story resumable See a resumable story

Works with Jira, GitHub, Claude Code, and Codex. Your story context remains readable Markdown.

The code is there. The reason behind it isn't.

You return to a story—or hand it to a teammate—after several AI sessions. Jira describes the request and GitHub shows the changes, but neither tells you what was tried, what failed, what evidence changed the plan, what remains uncertain, or what should happen next. The next person or AI session starts by reconstructing the previous one.

See a resumable story

This is a public-safe excerpt from Jesse's real CLI-only SCRUM-431 work record. It shows what the story actually retained; it is not a customer testimonial or a claimed outcome.

Allow sync commands to skip automatic backlog updatesSource: SCRUM-431 · CLI story record

Problem preserved

An automatic post-command update after pull or push could rewrite the backlog while another process was actively editing it.

Scope corrected

Source inspection showed that merge had no post-command update boundary. The story narrowed the change to pull and push instead of carrying a false assumption into implementation.

Decision recorded

Add a silent --skip-update option that bypasses only the automatic update. Provider and Git sync still run, and the default behavior remains unchanged.

Evidence attached

14 focused tests and 2,344 full-suite tests passed. Jira-backed dogfood with the built 0.95.0 CLI completed flagged pull and push without update output, while an unrelated sentinel story stayed byte-for-byte unchanged.

Outcome still open

Direct product-owner feedback remained open, so the record did not turn implementation evidence into a claim of confirmed user value.

Existing workflow proof

Try it on one real story.

Use a real, active Jira or GitHub story that is likely to be interrupted. HDD Light is the smallest guided product-learning and resumption loop: it keeps the problem, observable outcome, feedback path, evidence, compact plan approval, progress notes, deploy evidence, and close / iterate / pivot decision with fewer artifacts.

Start with one story and one teammate

This is a test to run—not a result we are claiming. Use one real handoff to learn whether the story record carries enough context.

Choose one active story
Pick work that is likely to cross an interruption or session boundary.
Hand it to one teammate
Ask one teammate to resume from the story record without replaying the previous AI sessions.
Review the resumption together
Use the five questions below to record what was clear, missing, or worth changing.

Run the complete path

Replace STORY-123 with one active Jira or GitHub story key. Setup is interactive, and your story context remains local Markdown in the repository.

npm install -g imdone-cli
imdone init
imdone hdd --light --resumability-test STORY-123
imdone push STORY-123

The --resumability-test flag enrolls only this story in the homepage experiment. Its key stays in personal local state and is not sent with experiment analytics.

See the complete eight-step HDD Light path

Choose one of your own stories
Pick real, active work rather than a sample generated by imdone.
Initialize and pull the story
imdone init performs the initial pull, bringing the current Jira or GitHub issue context into the repository as readable Markdown.
Start HDD Light
Launch your coding agent with the story in context and explicitly select the lightweight workflow.
Define the smallest outcome
Confirm the problem, what would be observably better, how feedback will be collected, and what evidence will show the result.
Approve a compact plan
Name the first boundary, important constraints, likely failure mode, and expected evidence before product-code changes begin.
Work and preserve progress
Keep meaningful decisions, blockers, corrections, completed work, evidence, and next steps with the story.
Deploy and close the loop
Record where the change is live, capture the result or feedback, and decide whether to close, iterate, or pivot.
Push the useful context and resume later
Sync the story record, then test whether a later human or AI session can continue without reconstructing the work.

Working on something high-risk or ambiguous?

Use imdone hdd STORY-123 for high-risk, ambiguous, cross-team, provider-sync-sensitive, or implementation-heavy work. HDD Light is the recommended first path for a low-risk story.

Make one story resumable

Did the story become easier to resume?

After an interruption, handoff, or fresh session, launch the same enrolled story again. The CLI confirms that this is a real resumption and asks these questions when you launch the same story again.

You do not need to return to this page. Judge the record—not the implementation—from what the later session could understand and continue.

Did the new session understand what had already happened?
Did it avoid reopening a rejected approach?
Was less time spent reconstructing context?
Was the next action clear?
Did the story preserve something that Jira and GitHub did not?

When one story works, test the workflow with a team.

Choose how to continue after the one-story test.

Self-serve software

Start on your own

Use Free, $9 Personal, or $18-per-user Team without a guided pilot. Keep using the same story workflow at your own pace.

See pricing

Optional guided team pilot

Test continuity with real team work

Run a structured 30-day pilot using your existing Jira workflow and coding agents. It includes Team software access during the pilot and guided evaluation—not payment for CLI access alone.

3–6 developers
Team software access during the pilot
One active team workflow
A defined set of stories
Guided setup and team onboarding
Weekly evidence reviews
Findings and rollout recommendation

30 days · $1,500

Discuss a team pilot

Opens an email with four short qualification prompts. You choose what to send.

Every story should be resumable.

Keep the decisions, failed attempts, evidence, blockers, and next step behind a Jira or GitHub story so you, a teammate, or another AI agent can continue without reconstructing what happened.

The code is there. The reason behind it isn't.

See a resumable story

Problem preserved

Scope corrected

Decision recorded

Evidence attached

Outcome still open

Try it on one real story.

Start with one story and one teammate

Choose one active story

Hand it to one teammate

Review the resumption together

Run the complete path

Choose one of your own stories

Initialize and pull the story

Start HDD Light

Define the smallest outcome

Approve a compact plan

Work and preserve progress

Deploy and close the loop

Push the useful context and resume later

Working on something high-risk or ambiguous?

Did the story become easier to resume?

When one story works, test the workflow with a team.

Start on your own

Test continuity with real team work

Developers who use imdone