jumppad-labs/jumppad
Overview
This skill creates detailed implementation plans through an interactive, iterative process. It guides context gathering, parallel research, design decisions, and produces structured deliverables including test strategies and success criteria. The approach is language-aware and delegates to language-specific guidelines when generating code examples and conventions.
How this skill works
The planner first detects project language and activates the appropriate guidelines for coding and testing. It spawns parallel research agents to explore the codebase, discover patterns, map architecture, and verify findings, then reads identified files fully and synthesizes results. After alignment with the user it produces a phased plan with task lists, code sketches following guidelines, testing strategy, migration notes, and measurable success criteria.
When to use it
- Planning a significant new feature or subsystem
- Designing a major refactor that touches multiple modules
- Preparing complex integrations with external services or infra
- Creating migration or rollout strategies (data/schema changes)
- When you need traceable plans linked to issue history and code references
Best practices
- Provide an issue number or file paths to start faster and link the plan to project history
- Allow the planner to run parallel research tasks for thorough, evidence-based recommendations
- Use the language-specific guideline activation step to ensure code examples follow project standards
- Keep working notes separate from deliverables; only finalized files go into the plan directory
- Review and validate drafts iteratively; request verification tasks for any user corrections
Example use cases
- Turn a GitHub issue into a full implementation plan with file:line references and task breakdowns
- Plan a Go microservice change with interface contracts, tests, and deployment steps using Go guidelines
- Draft a migration plan for a database schema change with rollback and data validation strategies
- Refactor auth flows across services with dependency mapping, performance checks, and security validation
- Create an ad-hoc plan for a prototype feature including test harness and success metrics
FAQ
It detects the project language and activates the matching guidelines to produce code examples and naming conventions that follow your project's standards.
What inputs speed up planning?
Providing an issue number, ticket reference, or relevant file paths enables immediate analysis and faster, more accurate plans with links to existing discussion and code.
2 skills
This skill creates thorough implementation plans through interactive research, design decisions, and structured deliverables to guide significant features and
This skill fetches complete GitHub issue context including description, comments, labels, assignees, milestones, and related PRs to inform planning.