agentleFS
drivestream-labdrivestream-lab/prayog-skills/skills/forge/create-board-tickets/SKILL.md

create-board-tickets

Skill2 starsChanged 4 months agoMITView on GitHub

After spec PR merge, seed the programme engineering board from Implementation Plan §9 WorkManifest: verify merge gate and board binding, present the EPIC/wave plan, then after explicit authorization create epic and wave issues. Human walker ForgeClient parity (create_board_tickets). Orchestrators use BoardService / ForgeClient on board-tickets-action — do not auto-invoke.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    One command after merge: read plan §9 → preflight → confirm → create.

    line 18
  2. Very specific:

    If missing, run launchpad board-bind --client <id> and stop.

    line 37
  3. Very specific:

    Never apply approval labels (*-lgtm).

    line 63
  4. Very specific:

    If tooling unavailable, print exact commands from references/output-template.md and stop — do not claim seeded.

    line 65
  5. Distinctive:

    Use references/output-template.md and references/checks.md (B1–B8).

    line 110
  6. Very specific:

    After successful seed, programme continues per pin (board-tickets-action pass → wave-in-progress-action → pre-implement).

    line 118
  7. Distinctive:

    Do not invent graph edges.

    line 120

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create board tickets

Human-walker equivalent of Gateflow board create (forge.action: create_board_tickets).

One command after merge: read plan §9 → preflight → confirm → create. There is no separate /board-seed content skill. At seed time WorkManifest lives in the implementation plan §9 (walk-time carrier). After successful seed, board issues are the long-term WorkManifest home — the plan file may be purged at initiative closure (prayog-skills/references/artifact-write-contract.md, prayog-skills/references/workmanifest-contract.md).

Do not run before spec merge. Do not write product code.

NON-NEGOTIABLE

  1. Resolve layout from .harness/profile.yaml or references/layout-defaults.md.
  2. Spec merge gate first — merged Implementation-Plan-{initiative}.md on integration branch; closed spec PR had spec-lgtm on merge head when verifiable.
  3. Board binding — resolve programme board from read-only meta governance: {workspace}/{meta_repo}/config/governance-*.yaml → project_board.name. If missing, run launchpad board-bind --client <id> and stop. Governance wins over plan §9 target.project free text.
  4. Validate WorkManifest before mutate — parse §9 YAML and run scripts/workmanifest_contract.py / validate_workmanifest for apiVersion: prayog/v1 + kind: WorkManifest. Require workmanifest-contract-pass (plan P16). Reject unsupported apiVersion/kind. Do not create issues on a failing contract. Require epic, work[] with wave ids W0…Wn, and each wave's tasks[] with stable TASK-*, implements, depends_on, exit proof, and verification as defined in prayog-skills/references/workmanifest-contract.md.
  5. Projection only — project epic/wave/task summaries from the canonical WorkManifest into board issue titles/bodies. After seed, board holds long-term identity; do not invent TASK ids, REQ mappings, dependencies, exit criteria, or proof summaries that are absent from §9 at seed time. Record created issue URLs/ids in the seed summary so /pre-implement can spend without requiring the plan file forever.
  6. Idempotent — search existing issues by initiative label; create only missing items; link existing waves under EPIC when parent missing.
  7. Hierarchy — EPIC first, then each wave as sub-issue on the same org Project. Initiative label on every issue. Wave bodies retain TASK ids, REQ mappings, dependencies, exit criteria, and proof summary from the manifest.
  8. Explicit authorization before mutate. Present the seed plan; create only after the human confirms. Authorization, branch, commit, PR, label, and issue-creation behavior otherwise unchanged.
  9. Never apply approval labels (*-lgtm). Tool-neutral Forge tooling (gh, project APIs, …) — examples only.
  10. If tooling unavailable, print exact commands from references/output-template.md and stop — do not claim seeded.
  11. Hosting gate — before create, verify every WorkManifest target repo (epic.repo / wave repo) has GitHub Issues enabled. If has_issues=false, print the exact enable-Issues fix and stop — do not claim seeded.
  12. Proof — after create, print every created issue URL (https://github.com/<org>/<repo>/issues/<n>) and verify each item is on the governance programme Project. B8 is blocking. No URL list ⇒ not seeded.
  13. Ids: prayog-skills/references/id-conventions.md. Paths: prayog-skills/references/artifact-write-contract.md. Checks: B1–B8.

Inputs

  1. Initiative id — (REQUIRED)
  2. Integration branch — (REQUIRED) default develop
  3. Merged plan — {reports_dir}/{plan_prefix}-{initiative}.md §9
  4. Meta governance — (REQUIRED) sibling meta clone / governance-<org>.yaml

Prerequisite

  • Spec PR merged; WorkManifest contract pass on §9 (workmanifest-contract-pass / P16)
  • Programme board configured (project_board.enabled + name)
  • Pin next step: board-tickets-action (forge.action: create_board_tickets)

Process

  1. T0 Gather — initiative, plan path, §9 YAML, governance board, repo slug, integration HEAD
  2. T1 Verify merge gate — plan on integration; optional closed spec PR with spec-lgtm; stop if still on open spec branch
  3. T1b Validate WorkManifest — run shared contract validator; stop on any structured error (unsupported version, DAG/exit/live violations)
  4. T2 Dedupe search — existing issues by initiative label (read-only)
  5. T3 Present seed plan — EPIC + waves + preserved TASK metadata summary, board name/URL, create vs existing; ask for authorization
  6. T4 Execute (authorized only) — create/update EPIC and waves; project links / sub-issues per board model; wave bodies carry projected TASK metadata from the manifest
  7. T5 Report — issue URLs; preserved task metadata; signals.seeded / already-seeded; handoff

Use references/output-template.md and references/checks.md (B1–B8).

Workflow handoff

  1. Append/emit envelope from prayog-skills/references/handoff-envelope.md. Stage id for this forge skill note: create-board-tickets (not a graph node).
  2. Dual-write handoff_path when bound.
  3. After successful seed, programme continues per pin (board-tickets-action pass → wave-in-progress-action → pre-implement). Do not invent graph edges.
  4. Honor pin requires on board-tickets-action (spec merged, plan current, workmanifest-contract-pass).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.