ratchet:sidequest

Records ad-hoc discoveries into the Ratchet plan's .ratchet/plan.yaml.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/netbrain/ratchet --skill ratchet-sidequest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratchet:sidequest
Source: https://github.com/netbrain/ratchet/tree/main/skills/sidequest
Command: npx skills add https://github.com/netbrain/ratchet --skill ratchet-sidequest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams run Ratchet-driven development there are often ad-hoc discoveries that occur mid-debate, mid-phase, or mid-milestone that are not captured by automated detectors. This skill provides a fast, manual way to record those findings into the Ratchet plan so they are tracked, surfaced, and processed like other sidequests without triggering debates or guards.

Core Features & Use Cases

  • Lightweight manual logging: Walks the user through a short interactive flow to capture a discovery description, category, severity, related pairs, and context.
  • Resilient plan updates: Reads and safely appends entries to .ratchet/plan.yaml, using yq when available and falling back to direct YAML edits with validation and rollback suggestions.
  • Contextual association: Attempts to auto-detect current milestone, issue, and active debate, and lets the user override or leave context blank; ideal for capturing CI surprises, review findings, or in-flight ideas.

Quick Start

Use /ratchet:sidequest to interactively log a new discovery into your project's ratchet plan.

Frequently Asked Questions about ratchet:sidequest

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

FAQPage Schema
How do I log ad-hoc discoveries into a ratchet plan.yaml file?

To log manual discoveries into a ratchet plan, use a workflow that interactively captures the description, category, severity, and context, then safely appends the entry to .ratchet/plan.yaml using yq or fallback file operations.

What is the best way to track mid-phase findings in a Ratchet-managed workspace?

Tracking mid-phase findings in a Ratchet-managed workspace involves recording sidequests directly into the plan.yaml file, capturing category, severity, related pairs, and timestamp without triggering automated debates or guards.

Can I manually record CI surprises or review findings without triggering Ratchet debates?

Yes, you can manually record CI surprises or review findings by logging them as sidequests into .ratchet/plan.yaml, which captures and surfaces discoveries for tracking without activating automated guards or debate workflows.

Do I need yq installed to update .ratchet/plan.yaml for sidequest tracking?

You do not need yq installed to update .ratchet/plan.yaml, as the logging process uses yq when available but falls back to direct YAML edits with validation and rollback suggestions to safely append entries.

How does manual discovery logging associate findings with milestones and issues?

Manual discovery logging auto-detects the current milestone, issue, and active debate within the Ratchet workspace, allowing you to override or leave context blank while associating the finding with specific agent pairs and a pending status.