rocket-plan

Automates software task implementation from intake to reviewed PR for Linear/Jira tickets and spec files.

Updated Jun 21, 2025
One-click install
npx skills add https://github.com/aryan-binazir/cc-config --skill rocket-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rocket-plan
Source: https://github.com/aryan-binazir/cc-config/tree/main/skills/personal_dev/rocket-plan
Command: npx skills add https://github.com/aryan-binazir/cc-config --skill rocket-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamline the end-to-end implementation process for Linear or Jira tickets, markdown spec files, or raw implementation specs, from intake through coding and into a reviewed PR.

Core Features & Use Cases

  • End-to-End Implementation: Clarify goals, settle contracts, and get pre-approval critiques.
  • Test-First Approach: Implement strictly test-first and push code for review.
  • Review Integration: Hand off to a configured rocket-review profile in the same session.
  • Optional Profile: Use with a specified profile for tailored review processes.

Quick Start

Use the rocket-plan skill to implement and review a Jira ticket, specifying an optional profile if needed.

Frequently Asked Questions about rocket-plan

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

FAQPage Schema
How do I automate Jira ticket implementation from intake to pull request?▼

Automating Jira ticket implementation involves streamlining intake, settling contracts, and utilizing a test-first development approach to push code for in-session review. This process clarifies goals and generates a reviewed pull request.

What is a test-first implementation flow for software tasks?▼

A test-first implementation flow requires writing tests before code, settling contracts for pre-approval, and conducting in-session code reviews. This ensures structured intake and code quality checks are met before pushing changes.

Can I use a markdown spec file to drive code review and implementation?▼

You can use markdown spec files or raw implementation specs to drive code review and implementation. The process clarifies goals, enforces test-first development, and hands off to a configured review profile within the same session.

How do I get pre-approval critiques before starting development on a ticket?▼

Getting pre-approval critiques involves settling contracts and clarifying goals during the intake phase before coding begins. This structured process ensures implementation aligns with specified profiles for tailored review.

Does end-to-end implementation work with Linear tickets and custom review profiles?▼

End-to-end implementation works with Linear tickets and supports specified profiles for tailored review processes. It automates intake, test-first development, and in-session code quality checks to produce reviewed pull requests.

What are the limitations of automating project management intake for software tasks?▼

Limitations include the strict requirement for structured intake and test-first development; automating project management intake fails without raw implementation specs or markdown files to settle contracts and drive in-session reviews.