create-continuation-prompt
Create Continuation Prompt
Generates a concise continuation prompt that captures the current session state, enabling seamless context clearing and session resumption.
Purpose
When context windows fill up or sessions need to be restarted, this skill creates a self-contained prompt that includes:
- Current task/objective
- Progress made so far
- Next steps
- Relevant file paths and locations
- Key decisions or constraints
Output Format
The continuation prompt is displayed as raw markdown, optimized for copy-paste into a new session.
Usage
/create-continuation-prompt
What Gets Included
Essential Information:
- Current working objective
- Files modified or created (with paths)
- Key decisions made
- Blockers or open questions
- Next immediate action
Excluded Information:
- Long code snippets (use file paths instead)
- Verbose explanations (keep concise)
- Completed context (focus on what's next)
Example Output
Continue working on auth implementation:
**Progress:**
- Added JWT validation to `src/api/handlers/auth.ts`
- Tests passing in `src/api/handlers/auth.test.ts`
**Next:**
- Add refresh token endpoint
- Update routes in `src/api/routes.ts:45`
**Constraint:** Only use jsonwebtoken library (no other auth libs)
Best Practices
- Keep it concise - Aim for <10 lines
- Use file paths - Reference code locations instead of copying code
- Focus forward - Emphasize next steps over past work
- Include constraints - Remind of critical rules or decisions
- Link resources - Include relevant URLs, PRs, or issue numbers
When to Use
- Context window approaching limits
- Switching between different work streams
- Before ending a work session
- After completing a milestone (to start fresh)
- When debugging requires a clean slate
Integration
Use alongside:
- Git commits (for checkpoint history)
- Task tracking (for broader project context)
- Documentation updates (for permanent records)
More from validkeys/sherpy
technical-requirements-interview
Conducts structured interviews to derive technical requirements from business requirements. Requires completed business-requirements.yaml as input. Asks targeted technical questions about architecture, technology stack, data model, APIs, security, testing, and deployment. Generates technical-requirements.yaml output.
48definition-of-done
Enhances milestones.yaml with detailed acceptance criteria for each milestone. Derives functional acceptance criteria, non-functional gates, testing requirements, documentation requirements, and exit checklists from business and technical requirements. Updates milestones.yaml in place with optional acceptance_criteria and exit_checklist fields.
30delivery-timeline
Generates a delivery timeline from a completed milestones.yaml. Asks for a production deploy date, QA rounds, and days per QA session. Updates each milestone with estimated_days, produces timeline.yaml with a complete relative-day schedule, and appends a workback block mapping every item to a real calendar date working backwards from the production deploy date.
30architecture-decision-record
Extracts key architectural decisions from technical-requirements.yaml and formalizes them as individual ADR markdown files in an adrs/ directory. Each ADR captures context, the decision made, alternatives considered, and consequences — creating a durable record of why the system is built the way it is.
30executive-summary
Generates an executive summary from planning artifacts for non-technical stakeholders. Auto-discovers business requirements, technical requirements, and timeline from the docs/ folder structure. Outputs a comprehensive summary covering business problem, solution, features, timeline, success metrics, risks, and resources.
23