continue

Resumes in-progress feature branches with their committed context and preview URLs.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill continue-evolutionary-leadership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continue
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/setup/railway/.claude/skills/continue
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill continue-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When work on a feature spans multiple sessions or teammates, resuming means reconstructing what was decided and where things stopped. This Skill lists active feature branches alongside their committed feature context, so you pick up mid-flow with the prior reasoning intact instead of re-deriving it from commit history. ## Core Features & Use Cases - Feature Discovery: Lists remote feature branches with last-commit summaries, open PRs against preprod, and Railway preview URLs. - Context-Aware Resume: Reads each branch's committed .harness/feature-context/<slug>.md file to show phase, next step, and open questions before you choose. - Safe Handover: Checks out a new session branch, sweeps stale context files, and delegates to the feature flow's resume logic rather than improvising one. - Use Case: A colleague parked a feature mid-review yesterday. Run the continue command, see their branch with its recorded next step and open questions, and resume exactly where they left off. ## Quick Start Ask the assistant to continue work on a feature, optionally naming it, for example: continue the user-authentication feature.

Frequently Asked Questions about continue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume work on a feature branch in Claude Code?

Run the continue command, optionally with a feature name. It lists remote feature branches with their last commit, open PRs, and preview URLs, then checks out a new session branch and hands off to the feature flow's resume logic.

How to see what a teammate was doing on a feature branch?

The skill reads the committed .harness/feature-context/<slug>.md file from the remote branch without checking it out, showing the recorded phase, next step, and open questions beside the git summary.

Does this work without the GitHub CLI installed?

Yes, with a fallback. Where gh is unavailable, open PRs are listed per the GitHub MCP note in docs/agents/issue-tracker.md, while all git operations work regardless.

What happens if a feature branch has no context file?

A branch without a context file predates the flow or skipped it. The skill says so explicitly rather than guessing at the branch's state, so you know the resume will lack recorded reasoning.

What does a parked or blocked feature mean when resuming?

A parked label means the change stopped at a gate and resumes only if you un-park it. A Blocked section means the last session stood down; read it first and clear it only once the block is actually gone.