Add create-issues skill; delegate init-project's issue creation to it #14

Closed
opened 2026-08-17 06:56:03 +00:00 by david · 0 comments
Owner

Description

Adds a new create-issues skill that converts a local implementation plan
(.md) into a milestone-structured set of fully self-contained issues on
Forgejo, GitLab, or GitHub, and updates init-project to delegate to it.

Tasks

  • Add skills/create-issues/SKILL.md: local-plan input, host detection
    (piloop-config.yaml git-host override, else git-remote auto-detect),
    per-host tooling (gh, the forgejo pi extension, glab), milestone
    modeling per host (GitHub = milestone:<slug> labels, Forgejo = native
    via the forgejo extension's milestone/label tools with a fail-fast
    dependency check, GitLab = native glab milestone create), step
    granularity rules, self-contained issue template (Summary / Background
    / Documentation Required / Implementation Details / Acceptance Criteria
    / Test Plan), dependency backfilling, and preview+confirm+idempotent
    creation.
  • Update skills/init-project/SKILL.md Phase 3 (and Quick Reference) so
    init-project keeps creating its own repository-setup issue directly, but
    delegates the plan's actual milestones/steps to the new create-issues
    skill instead of its own inline flat-list logic.

Acceptance Criteria

  • skills/create-issues/SKILL.md exists and documents the full plan-to-
    issues flow described above
  • skills/init-project/SKILL.md Phase 3 delegates to create-issues and
    no longer contains the old inline "parse plan into issues" logic
  • Both files are internally consistent (no dangling references to the old
    flow)

Verification

Read through both SKILL.md files and confirm the described phases/flow are
complete and consistent; no code execution required (these are skill
definition/documentation files).

  • #13 — tracks the separate forgejo-extension dependency (milestone
    create/list + label create tools) that create-issues' Forgejo path
    requires at runtime; not implemented as part of this issue.
## Description Adds a new `create-issues` skill that converts a local implementation plan (`.md`) into a milestone-structured set of fully self-contained issues on Forgejo, GitLab, or GitHub, and updates `init-project` to delegate to it. ## Tasks - [x] Add `skills/create-issues/SKILL.md`: local-plan input, host detection (`piloop-config.yaml` `git-host` override, else git-remote auto-detect), per-host tooling (`gh`, the `forgejo` pi extension, `glab`), milestone modeling per host (GitHub = `milestone:<slug>` labels, Forgejo = native via the forgejo extension's milestone/label tools with a fail-fast dependency check, GitLab = native `glab milestone create`), step granularity rules, self-contained issue template (Summary / Background / Documentation Required / Implementation Details / Acceptance Criteria / Test Plan), dependency backfilling, and preview+confirm+idempotent creation. - [x] Update `skills/init-project/SKILL.md` Phase 3 (and Quick Reference) so init-project keeps creating its own repository-setup issue directly, but delegates the plan's actual milestones/steps to the new `create-issues` skill instead of its own inline flat-list logic. ## Acceptance Criteria - [ ] `skills/create-issues/SKILL.md` exists and documents the full plan-to- issues flow described above - [ ] `skills/init-project/SKILL.md` Phase 3 delegates to `create-issues` and no longer contains the old inline "parse plan into issues" logic - [ ] Both files are internally consistent (no dangling references to the old flow) ## Verification Read through both `SKILL.md` files and confirm the described phases/flow are complete and consistent; no code execution required (these are skill definition/documentation files). ## Related - #13 — tracks the separate forgejo-extension dependency (milestone create/list + label create tools) that `create-issues`' Forgejo path requires at runtime; not implemented as part of this issue.
david closed this issue 2026-08-18 01:56:43 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
david/pi-extensions-and-skills#14
No description provided.