Sks Issue Workflow

Shikanime Org Issue Workflow

Thin orchestrator over sks-issue → sks-issue-refine → sks-issue-triage.

When to Use

• "Open and set up an issue on ".
• "Take this problem through to a triaged issue".
• "Run the issue side: create an issue and triage it."
• "Derive the PR" — after refinement converges on a statable problem.
• "Set up the full issue workflow before implementation."

Procedure

1. Create — Load sks-issue. Body = problem statement + - [ ] gate ledger (command-decidable acceptance criteria); findings go in comments, not the body. Result: issue #N.
2. Refine — Load sks-issue-refine; iterate the problem inside the issue until acceptance criteria converge. Update the body's tasklist only when criteria change. Skip only if already converged at creation (rare).
3. Triage — Load sks-issue-triage; apply labels, assignee, milestone, project now. Only empty/determinable fields — never invent a label the repo lacks.

Gate

Complete when body is a stable problem statement with a converged - [ ] ledger and triage metadata is set. Verify:

gh issue view <N> --repo <org>/<repo> --json number,title,labels

Verification

gh issue view <N> --repo <org>/<repo> --json number,title,labels \
  # body + ledger + triage set

See also

• sks-issue — create step.
• sks-issue-refine — in-issue convergence loop.
• sks-issue-triage — metadata step run immediately after creation.