npx claudepluginhub pragnition/pragnition-public-plugins --plugin rapidThis skill is limited to using the following tools:
You are the RAPID resume handler. This skill resumes a previously paused set by loading its HANDOFF.md and STATE.json context, allowing execution to continue from where it left off. Follow these steps IN ORDER. Do not skip steps.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
You are the RAPID resume handler. This skill resumes a previously paused set by loading its HANDOFF.md and STATE.json context, allowing execution to continue from where it left off. Follow these steps IN ORDER. Do not skip steps.
if [ -z "${RAPID_TOOLS:-}" ] && [ -n "${CLAUDE_SKILL_DIR:-}" ] && [ -f "${CLAUDE_SKILL_DIR}/../../.env" ]; then export $(grep -v '^#' "${CLAUDE_SKILL_DIR}/../../.env" | xargs); fi
if [ -z "${RAPID_TOOLS}" ]; then echo "[RAPID ERROR] RAPID_TOOLS is not set. Run /rapid:install or ./setup.sh to configure RAPID."; exit 1; fi
echo "Environment loaded. RAPID_TOOLS=${RAPID_TOOLS}"
If the user provided a set name as argument (/rapid:resume {setName} or /rapid:resume 1):
Resolve the set argument through the numeric ID resolver:
# (env preamble here)
RESOLVE_RESULT=$(node "${RAPID_TOOLS}" resolve set "<user-input>" 2>&1)
RESOLVE_EXIT=$?
if [ $RESOLVE_EXIT -ne 0 ]; then
echo "$RESOLVE_RESULT"
# Display the error message from the JSON and STOP
fi
SET_NAME=$(echo "$RESOLVE_RESULT" | node -e "d=JSON.parse(require('fs').readFileSync(0,'utf-8')); console.log(d.resolvedId)")
Use SET_NAME for all subsequent operations. Skip to Step 3.
If no set name was provided, list paused sets:
node "${RAPID_TOOLS}" worktree list 2>/dev/null
Parse the JSON output and filter for entries with phase: "Paused".
If multiple paused sets: Use AskUserQuestion with:
If exactly one paused set: Use that set automatically and inform the user: "Found one paused set: {setName}"
If no paused sets: Print: "No paused sets found. Use /pause to pause an executing set first." and end.
Call the resume CLI with --info-only to load handoff data and STATE.json context without transitioning the set's phase:
node "${RAPID_TOOLS}" resume --info-only {setName}
Parse the JSON output which contains:
resumed: boolean (will be false since --info-only does not transition state)setName: the set namehandoff: parsed HANDOFF.md data (frontmatter + sections)stateContext: wave/job progress from STATE.json (may be null)definitionPath: path to DEFINITION.mdcontractPath: path to CONTRACT.jsonpauseCycles: number of times this set has been pausedIf the command fails (set not in Paused phase or HANDOFF.md missing): Display the error and end.
Present the handoff data in a clear format:
Resuming Set: {setName}
Pause Cycle: {pauseCycles} Last Action: {handoff.frontmatter.handoff_done or 'Not recorded'} Remaining Work: {handoff.frontmatter.handoff_remaining or 'Not recorded'} Pause Notes: {handoff.frontmatter.handoff_resume or 'No notes'}
Wave/Job Progress: {Format stateContext.waves showing completion status per wave, or 'No state context available'}
Use AskUserQuestion with:
If "View HANDOFF.md": Read and display the file:
cat .planning/sets/{setName}/HANDOFF.md
Then ask again with AskUserQuestion:
If "Cancel": Print "Resume cancelled. Set remains paused." and end.
Now that the user has confirmed, call the resume CLI without --info-only to transition the set from Paused to Executing:
node "${RAPID_TOOLS}" resume {setName}
If the command fails: Display the error and end.
The resume CLI (Step 6) has transitioned the set from Paused to Executing in REGISTRY.json.
Display the resume confirmation:
Set '{setName}' resumed.
- Worktree: {worktree path from registry}
- Branch: rapid/{setName}
- Phase: Executing
The set is ready for continued execution. Run
/execute {setName}to proceed from where the previous session left off.The executor will receive the HANDOFF.md context automatically and continue from the first incomplete task.
resume CLI command (without --info-only) updates REGISTRY.json phase from Paused to Executing. The --info-only flag loads handoff data without transitioning state, used in Step 3 before user confirmation.