feature-continue
npx machina-cli add skill YoniChechik/claude-code-config/feature-continue --openclawContinues work on an existing feature clone with proper context analysis.
Feature description from user input
"$ARGUMENTS"
Feature Description Validation
If empty or missing: "Error: Feature description is required. Please provide a detailed description of the feature you want to continue implementing."
Process
Step 1: Search for Existing Clone
List existing clones in _clones/ directory and try to match the feature description:
ls -1 _clones/
If found → Continue to Step 3 (navigate) If not found → Continue to Step 2
Step 2: Check for Remote Branch
Check if a remote feature branch exists that matches the description:
git fetch --prune
git branch -r
Review the list of remote branches and match one to the user's feature description.
If found → Run /create-clone with the matched branch name, then continue to Step 4
If not found → Exit with error:
- Tell user: "Feature branch not found locally or remotely"
- Suggest: "Use /create-clone <feature-description> to create a new feature clone"
Step 3: Navigate to Feature Clone
cd _clones/FEATURE_NAME
Step 4: Gather Context & Analyze Status
Determine feature name from branch: FEATURE_NAME=$(git rev-parse --abbrev-ref HEAD)
- Use explorer subagent to understand the codebase relevant to the feature
- Check if
plan_$FEATURE_NAME.mdexists — if yes, read it - Run
git diff origin/main...HEADto see what's been done so far - Compare progress against the plan (if exists)
Step 5: Check State & Report
- Check git branch state:
bash ~/.claude/scripts/git_branch_state.sh
- Report to the user:
- What the feature is about (from plan or branch name)
- What has been done so far (from git diff)
- Git branch state (diverged? behind main?)
- Read and understand the full development workflow:
- Read the file
~/.claude/skills/feature-loop-scheme/SKILL.mdto understand how we work - Based on current progress, tell the user where we are in that workflow
- Read the file
- Suggest next steps:
- If behind main or diverged → suggest running
/syncfirst - Tell the user what the next step in the workflow would be
- If behind main or diverged → suggest running
STOP HERE. Do NOT proceed to implementation. Wait for user instructions on what to do next.
Source
git clone https://github.com/YoniChechik/claude-code-config/blob/main/skills/feature-continue/SKILL.mdView on GitHub Overview
Feature-continue resumes work on an existing feature clone by analyzing the current codebase, its plan, and progress. It searches for the matching clone, checks for a remote branch, gathers context, and reports on the state to guide next steps.
How This Skill Works
Starts by finding a clone that matches the feature description in the _clones directory. If a matching local clone isn’t found, it checks remote branches for a corresponding feature. It then navigates into the clone, derives the feature name from the branch, compares progress with the plan using a diff against origin/main, and reports the feature scope, progress, and branch state before stopping.
When to Use It
- You have a local feature clone and need to resume work after an interruption
- There is a remote feature branch that matches the description but no local clone
- You want a status update comparing plan vs. actual changes
- The clone’s branch is behind main or diverged and you need guidance before coding
- You’re about to continue implementation and want a clear next-step plan
Quick Start
- Step 1: Identify a matching clone (local) or remote branch for the feature
- Step 2: Navigate to the clone, derive FEATURE_NAME, and read plan_$FEATURE_NAME.md if present
- Step 3: Run a diff against origin/main and review branch state to decide next steps
Best Practices
- Verify the feature description exactly matches the clone and branch
- Check for an existing plan file plan_$FEATURE_NAME.md and read it first
- Use git diff origin/main...HEAD to measure progress
- Run the provided state checks (git_branch_state) to understand branch health
- Follow the feature-loop workflow docs before making changes
Example Use Cases
- Resuming a login feature clone after a sprint break
- Continuing a data import feature when a matching remote branch exists
- Reviewing a UI feature clone with an up-to-date plan file
- Handling a feature whose branch has diverged from main
- Preparing to implement a feature after confirming the next steps
