Find Unplanned Issues
Audit and clean the Remotion GitHub masterplan hierarchy. Use when finding open issues that lack a masterplan ancestor, identifying orphaned issues that need a parent, or recursively removing closed issues from the masterplan rooted at issue #9081.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Find Unplanned Issues when an AI agent needs a reusable SKILL.md workflow for this job: Audit and clean the Remotion GitHub masterplan hierarchy. Use when finding open issues that lack a masterplan ancestor, identifying orphaned issues that need a parent, or recursively removing closed issues from the masterplan rooted at issue #9081.
When not to use it
Skip Find Unplanned Issues when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/find-unplanned-issues # Save SKILL.md to ~/.claude/skills/find-unplanned-issues/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/find-unplanned-issues/SKILL.md. For a shared project, commit the folder at .claude/skills/find-unplanned-issues/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Find Unplanned Issues skill for this task: Use Find Unplanned Issues when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Find unplanned issues
Run the bundled read-only audit from the repository root:
```sh bun .agents/skills/find-unplanned-issues/scripts/find-unplanned-issues.ts ```
The script treats an issue as planned when its title contains `masterplan` or any issue in its parent chain has a title containing `masterplan`. Masterplan issues themselves are omitted from the report. Repository-specific exceptions are also omitted; currently, issue #8375 is exempt because the long-running CI flake tracker intentionally stands on its own. Results distinguish between:
- `no parent`: the open issue has no parent at all. - `no masterplan ancestor`: the issue has a parent, but following the complete parent chain does not reach a masterplan.
Use a different repository or machine-readable output when needed:
```sh bun .agents/skills/find-unplanned-issues/scripts/find-unplanned-issues.ts --repo owner/repo bun .agents/skills/find-unplanned-issues/scripts/find-unplanned-issues.ts --json ```
Pass `--check` for automation. It exits with status 1 when unplanned issues are found and 0 when every non-exempt open issue belongs to a masterplan.
The audit requires an authenticated `gh` CLI that supports the `parent` JSON field. It only reads issue data. To fix findings, use the `issue-management` skill and verify each relationship after editing it.
## Remove closed issues from the masterplan
Preview all closed descendants of the root masterplan recursively:
```sh bun .agents/skills/find-unplanned-issues/scripts/prune-closed-masterplan-issues.ts ```
The default root is <https://github.com/remotion-dev/remotion/issues/9081>. Override it only when intentionally auditing a different hierarchy:
```sh bun .agents/skills/find-unplanned-issues/scripts/prune-closed-masterplan-issues.ts \ --root https://github.com/owner/repo/issues/123 ```
The command is a dry run unless `--apply` is passed. During application, process closed issues deepest-first and verify every relationship after changing it. If a closed issue has open children, move those children to its parent before removing the closed issue so open work stays in the masterplan.
```sh bun .agents/skills/find-unplanned-issues/scripts/prune-closed-masterplan-issues.ts --apply ```
Use `--json` for a machine-readable dry-run report. Never pass `--apply` merely to test the script; it changes live GitHub issue relationships.
Intended uses
- Use Find Unplanned Issues when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.