What problem does it solve?
Contributors often jump into implementation without confirming scope, ownership, or acceptance criteria, leading to misaligned pull requests and rework. This Skill produces an evidence-based, read-only plan that divides a NemoClaw GitHub issue into independently valuable capability slices before any code is written.
Core Features & Use Cases
- Evidence-Based Issue Planning: Fetches the issue, current source, tests, workflows, and related PRs to confirm scope authority, current behavior ownership, and delivery constraints before planning.
- Capability Slicing: Breaks the issue into slices that each deliver one independently valuable outcome, with acceptance examples, dependencies, test plans, and deferred scope recorded per slice.
- Controlled GitHub Writes: Planning is read-only by default; any authorized write (labels, comments, assignments) is previewed exactly, performed once, and reported with its URL or failure.
- Use Case: A contributor receives a vague feature request as issue #8378. They run the planning workflow to confirm the accepted scope, identify the current behavior owner, define observable acceptance examples, and select the first slice worth delivering—without touching source code.
Quick Start
Ask the agent to plan NemoClaw issue #8378 and return the structured report with capability slices and the first slice to deliver.
