skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sonnet

Execute procedural implementation plans for the JellyRock Roku client on the Sonnet model.

37|2|Updated Jun 28, 2025
Search Tags:#commit#implementation#verification#plan#tokens#sonnet#jellyrock
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill sonnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sonnet
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/sonnet
Command: npx skills add https://github.com/jellyrock/jellyrock --skill sonnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the wasted token cost of running fully-specified, procedural implementation plans on high-judgment models, freeing up reasoning budget for work that actually requires architectural decision-making and open-ended problem solving.

Core Features & Use Cases

  • Token-Efficient Plan Execution: Runs pre-written implementation plans on the Sonnet model instead of high-judgment Opus-class models, reducing token consumption for low-complexity procedural work.
  • Strict Scope Enforcement: Only edits files listed in the plan's Critical files table, preventing unintended scope creep and accidental changes to unrelated code.
  • Use Case: You have a /focus-generated plan for a small bug fix or feature tweak with all architectural decisions already resolved; use this skill to implement, verify, and commit the changes without manual step-by-step oversight.

Quick Start

Use the sonnet skill by providing the path to your completed implementation plan to automatically execute all planned edits, run project verification checks, and draft a commit for your approval.

Frequently Asked Questions about sonnet

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

FAQPage Schema
How do I reduce token costs when executing procedural implementation plans?▼

Yes, you can execute fully-specified procedural implementation plans on the Sonnet model to reduce token consumption for low-complexity work while preserving reasoning budget for architectural decisions.

How do I enforce strict scope adherence when executing a written implementation plan?▼

Strict scope adherence is enforced by restricting edits exclusively to files listed in the plan's Critical files table, preventing unintended scope creep and accidental changes to unrelated code.

When should I not use Sonnet for implementation plan execution?▼

Avoid using Sonnet for implementation plan execution when working with open forks, high blast radius changes, or unresolved planning questions, as these tasks require high-judgment model reasoning and architectural decision-making.

Can I automate verification gates and commit drafting for pre-written implementation plans?▼

Yes, you can automate mandatory verification gate execution and pre-push commit review by providing the path to a completed implementation plan, which drafts a commit for approval after running project verification checks.

What is required before running an implementation plan on the Sonnet model?▼

Before running an implementation plan on the Sonnet model, you need a fully-specified procedural plan with all architectural decisions resolved, including defined Critical files and Verification gates.

Related Skills

Explore More Software Engineering Skills→
denis-pingindenis-pingin

fixme-execute-plan

Execute implementation plans with per-step verification and gated commits.

Community
Advanced
BigdropsBigdrops
1

gitnexus-impact-analysis

Analyze code change impact and identify dependencies and risks.

Community
Advanced
vivshawvivshaw
2

using-generic-agents

Assess task complexity and select Haiku, Sonnet, or Opus agent types.

Community
Intermediate
wonderslifewonderslife
13

openspec-explore

Guide requirement clarification through codebase exploration and ASCII diagrams.

Community
Basic