Create plan and triage skills from automations #567

Merged
Vylpes merged 1 commit from feature/plan-triage-skills into release/0.12.0 2026-10-11 13:03:37 +01:00
Owner
  • Create plan and triage skills from automations so that we can manually run the same flows when required
- Create plan and triage skills from automations so that we can manually run the same flows when required
Create plan and triage skills from automations
All checks were successful
Test / build (push) Successful in 1m58s
be77c31c3a
Smithy-bot approved these changes 2026-10-11 12:04:38 +01:00
Smithy-bot left a comment

Review: plan/triage skills from automations

Verdict: Approve — This is documentation-only (.cursor/skills) and the refactor is coherent.

Summary

  • Replaces standalone generate-criteria and generate-test-plan with plan-issue, which walks the full needs/* ladder (criteria → estimate → test → approval) in one skill aligned with the planning runner.
  • Adds triage-issue for idea/epic/investigation/spike/alert/incident work, with clear redirects (needs/* → plan-issue; dev types out of scope).
  • Both skills keep the important guardrails: explore the codebase, draft in chat, no Forgejo mutations until the user approves, and explicit handling of the question label when blocked.

What looks good

  • Planning ladder table and per-step mutate actions match how the automation should behave manually.
  • triage-issue avoids duplicating linked children and leaves new stories unassigned with needs/criteria.
  • Examples are card-drop–specific (#543 epic, management UI docs) rather than generic calculator copy.
  • Test plans under needs/test stay as issue comments (consistent with not committing docs/test-plans/ in this flow).

Minor (non-blocking)

  • Hardcoded External label ids (292, 293, 322, …) may drift; the “verify if missing” note is enough for now.
  • If anything outside this PR still documents the old skill names (generate-criteria, generate-test-plan), update those references in a follow-up.

No runtime code changes; safe to merge into release/0.12.0.

## Review: plan/triage skills from automations **Verdict: Approve** — This is documentation-only (`.cursor/skills`) and the refactor is coherent. ### Summary - Replaces standalone `generate-criteria` and `generate-test-plan` with **`plan-issue`**, which walks the full `needs/*` ladder (criteria → estimate → test → approval) in one skill aligned with the planning runner. - Adds **`triage-issue`** for idea/epic/investigation/spike/alert/incident work, with clear redirects (`needs/*` → `plan-issue`; dev types out of scope). - Both skills keep the important guardrails: explore the codebase, draft in chat, **no Forgejo mutations until the user approves**, and explicit handling of the `question` label when blocked. ### What looks good - Planning ladder table and per-step mutate actions match how the automation should behave manually. - `triage-issue` avoids duplicating linked children and leaves new stories unassigned with `needs/criteria`. - Examples are card-drop–specific (#543 epic, management UI docs) rather than generic calculator copy. - Test plans under `needs/test` stay as issue comments (consistent with not committing `docs/test-plans/` in this flow). ### Minor (non-blocking) - Hardcoded External label ids (292, 293, 322, …) may drift; the “verify if missing” note is enough for now. - If anything outside this PR still documents the old skill names (`generate-criteria`, `generate-test-plan`), update those references in a follow-up. No runtime code changes; safe to merge into `release/0.12.0`.
Vylpes merged commit 947b588445 into release/0.12.0 2026-10-11 13:03:37 +01:00
Vylpes deleted branch feature/plan-triage-skills 2026-10-11 13:03:37 +01:00
Sign in to join this conversation.
No description provided.