scope-spinoff

Create Backlog issues from selected side findings and update the parent issue.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/iamacoffeepot/aether --skill scope-spinoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-spinoff
Source: https://github.com/iamacoffeepot/aether/tree/main/.agents/skills/scope-spinoff
Command: npx skills add https://github.com/iamacoffeepot/aether --skill scope-spinoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps streamline the process of taking side findings from an Aether scope and spinning them off into individual Backlog issues.

Core Features & Use Cases

  • Side Finding Triage: Identify and categorize side findings from a parent issue.
  • Issue Creation: Create separate Backlog issues for each selected side finding.
  • Parent Issue Update: Update the parent issue body to reflect the spinoff process.

Quick Start

To initiate the spinoff process, use the 'scope-spinoff' skill and specify the indices of the side findings you want to spin off.

Frequently Asked Questions about scope-spinoff

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

FAQPage Schema
How do I spin off side findings from a parent issue into separate backlog issues?

To spin off side findings, you select specific findings within a parent issue and use the scope-spinoff skill to automatically create individual backlog issues for each one. The parent issue body is then updated to reflect the items that were spun off.

What is the best way to manage scope creep and triage side findings in issue tracking?

Managing scope creep by triaging side findings involves identifying out-of-scope items within a parent issue and spinning them off into distinct backlog issues. This keeps the original issue focused while ensuring new findings are tracked separately.

Can I select specific side findings to spin off while leaving others in the parent issue?

Yes, you can select specific side findings to spin off by specifying their indices when initiating the process. Only the selected findings are extracted into new backlog issues, leaving the rest untouched in the parent issue.

Does scope management for backlog triage require specific environment setup?

Scope management for backlog triage requires the Aether engine environment to function. It operates within this engine to identify side findings, create the individual backlog issues, and update the parent issue body accordingly.

How does the parent issue get updated after spinning off side findings?

After spinning off side findings, the parent issue gets updated automatically by modifying its body to reflect the spinoff process. This ensures the original issue maintains a clear record of what scope was extracted into separate backlog issues.