bounce

Regress an Aether issue to an earlier phase with a required reason.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bounce skill addresses the need for a streamlined process to regress Aether issues to an earlier phase when it becomes necessary to redo Define, Design, or Plan stages due to new insights or changes in scope.

Core Features & Use Cases

  • Issue Regression: Bounce an issue back to an earlier phase with a required reason.
  • Required Reason: Ensures that the decision to regress an issue is justified and documented.
  • Use Case: When a developer or team member realizes that a feature or fix requires re-evaluation or rework in the Define, Design, or Plan phases, they can use this skill to regress the issue with a clear explanation.

Quick Start

To regress an issue to the Design phase, use the command: bounce issue_id -to phase:design -reason "Detailed reason for regression."

Frequently Asked Questions about bounce

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

FAQPage Schema
How do I move an Aether issue back to an earlier phase?

To regress an Aether issue to an earlier phase, use the bounce command with a target phase and a detailed reason. This moves the issue back to Define, Design, or Plan stages and records the justification.

When should I regress an issue to the Define or Design phase?

You should regress an issue to the Define, Design, or Plan phase when scope changes, implementation hurdles, or review feedback indicate the original requirements need re-evaluation or rework.

Do I need to provide a reason when regressing an Aether issue?

Yes, providing a clear reason for issue regression is required. The workflow ensures every decision to move an issue back to an earlier phase is justified, properly labeled, and documented with a comment.

How do I document issue regression in Aether workflows?

Issue regression is documented by specifying a detailed reason in the bounce command. The system automatically labels the regressed issue and adds a comment to maintain a clear audit trail.

Can I re-evaluate the Plan phase after implementation has started?

Yes, you can re-evaluate the Plan phase after implementation starts. If review or implementation reveals a need to redo earlier stages, you can regress the issue back to the Plan phase with a documented reason.