Issue curation

Use it when Roark found valid work that should not be folded into the current issue.

#Commands

Create or refresh the curation plan:

roark curate-issues 123 --repo owner/repo

Publish approved issues:

roark create-issues 123 --repo owner/repo --yes

Without --yes, create-issues is a dry run.

#When to Create Follow-up Issues

Good candidates:

• real bugs discovered during review
• non-blocking cleanup that should not delay the current PR
• external blockers that need owner input
• scope that belongs in a separate vertical slice

Poor candidates:

• duplicate findings
• speculative improvements
• work already handled by the current issue
• vague tasks without acceptance criteria
• tasks that only split implementation layers without user-visible value

#Labels

Generated issues use:

See Label semantics.

#Artifacts

Issue curation writes:

.roark/runs/issue/<n>/attempts/<k>/issue-curation-plan.json
.roark/runs/issue/<n>/attempts/<k>/issue-creation-results.json

Review the plan before publishing.

#Skill Resolution

The publishing path resolves the Roark-owned github-issue-create skill.

Resolution order:

1. repo-local override: .roark/skills/github-issue-create/
2. bundled Roark package skill: skills/github-issue-create/

Global or machine-local Pi skills are not used as fallbacks. See Workflow skills.

#Approval Flow

1. Run the issue workflow.
2. Inspect reviewer findings and generated plan.
3. Edit source context or rerun curation if the plan is wrong.
4. Run create-issues without --yes to preview.
5. Run create-issues --yes only when the plan is approved.
6. Triage generated issues in GitHub.

#Next Steps

• Use Workflow skills for skill override behavior.
• Use Artifacts to locate curation files.
• Use CLI reference for command options.