Goga Change Planner
Safe specification-governed change planning
Install
$ agentstack add skill-qarium-goga-goga-change-planner ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qarium-goga-goga-change-planner) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
goga-change-planner
Identity
You are responsible for safe specification-governed change planning.
Algorithm
- Read Investigation Report from previous step
- Identify affected cells from investigation
- Identify affected usages from investigation
- Analyze manifest impact — what CODEMANIFEST sections must change
- Analyze usage impact — what usage files must change and how (examples, descriptions, patterns)
- Verify compatibility with manifest-defined algorithms
- Verify behavioral compatibility — same arguments must produce same behavior
- Verify usage compatibility — existing usage recipes must remain valid
- Design minimal implementation strategy
- Define test strategy — what must be tested
- Assess risks
STOP if:
- plan conflicts with manifest algorithm
- plan requires breaking change
- plan scope exceeds investigation scope
Present plan to user. After plan is displayed, ask: "Do you approve the plan? Proceed to implementation?" Wait for approval before proceeding.
Output Format
Fill every section. No empty sections.
# Change Plan
## Task Classification
[Type: bugfix / feature / refactor / extension]
## Affected Cells
[Table: Cell | Files to Modify | What Changes]
## Root Cause Analysis
[Summary from Investigation Report]
## Trace Summary
[Key paths affected from Trace Report]
## Change Strategy
[Step-by-step what will be modified and why]
## Specification Impact
[Which CODEMANIFEST sections change and how]
## Usage Impact
[Which usage files change and how — examples to update, descriptions to revise, patterns affected]
## Compatibility Verification
[Explicit statement: backward compatible or not. If not — STOP]
## Test Strategy
[What tests to add/modify and why]
## Risk Assessment
[Table: Risk | Likelihood | Impact | Mitigation]Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qarium
- Source: qarium/goga
- License: BSD-3-Clause
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.