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.
In this repository22 other files it gives its agents.
- ground-specSkill
- initiative-feasibilitySkill
- learning-extractSkill
- loop-specSkill
- pre-implementSkill
- purge-initiative-artifacts-appSkill
- spec-draftSkill
- spec-implementation-planSkill
- spec-technical-reviewSkill
- ensure-repo-graphSkill
- post-product-questionsSkill
- prd-codebase-mapSkill
- review-product-questionsSkill
- commit-workspaceSkill
- open-draft-prSkill
- prd-impact-mapSkill
- prd-qualitySkill
- prd-thinkSkill
- purge-initiative-artifacts-metaSkill
- review-findingsSkill
- update-documentsSkill
- validate-requirementsSkill
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
- Very specific: line 18
One command after merge: read plan §9 → preflight → confirm → create.
- Very specific: line 37
If missing, run launchpad board-bind --client <id> and stop.
- Very specific: line 63
Never apply approval labels (*-lgtm).
- Very specific: line 65
If tooling unavailable, print exact commands from references/output-template.md and stop — do not claim seeded.
- Distinctive: line 110
Use references/output-template.md and references/checks.md (B1–B8).
- Very specific: line 118
After successful seed, programme continues per pin (board-tickets-action pass → wave-in-progress-action → pre-implement).
- Distinctive: line 120
Do not invent graph edges.
≈ “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.
Files
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
- Resolve layout from
.harness/profile.yamlor references/layout-defaults.md. - Spec merge gate first — merged
Implementation-Plan-{initiative}.mdon integration branch; closed spec PR hadspec-lgtmon merge head when verifiable. - Board binding — resolve programme board from read-only meta governance:
{workspace}/{meta_repo}/config/governance-*.yaml→project_board.name. If missing, runlaunchpad board-bind --client <id>and stop. Governance wins over plan §9target.projectfree text. - Validate WorkManifest before mutate — parse §9 YAML and run
scripts/workmanifest_contract.py/validate_workmanifestforapiVersion: prayog/v1+kind: WorkManifest. Requireworkmanifest-contract-pass(plan P16). Reject unsupportedapiVersion/kind. Do not create issues on a failing contract. Requireepic,work[]with wave idsW0…Wn, and each wave'stasks[]with stableTASK-*,implements,depends_on, exit proof, and verification as defined inprayog-skills/references/workmanifest-contract.md. - 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-implementcan spend without requiring the plan file forever. - Idempotent — search existing issues by initiative label; create only missing items; link existing waves under EPIC when parent missing.
- 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.
- 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.
- Never apply approval labels (
*-lgtm). Tool-neutral Forge tooling (gh, project APIs, …) — examples only. - If tooling unavailable, print exact commands from
references/output-template.md and stop —
do not claim
seeded. - Hosting gate — before create, verify every WorkManifest target repo
(
epic.repo/ waverepo) has GitHub Issues enabled. Ifhas_issues=false, print the exact enable-Issues fix and stop — do not claimseeded. - 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. - Ids:
prayog-skills/references/id-conventions.md. Paths:prayog-skills/references/artifact-write-contract.md. Checks: B1–B8.
Inputs
- Initiative id — (REQUIRED)
- Integration branch — (REQUIRED) default
develop - Merged plan —
{reports_dir}/{plan_prefix}-{initiative}.md§9 - 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
- T0 Gather — initiative, plan path, §9 YAML, governance board, repo slug, integration HEAD
- T1 Verify merge gate — plan on integration; optional closed spec PR with
spec-lgtm; stop if still on open spec branch - T1b Validate WorkManifest — run shared contract validator; stop on any structured error (unsupported version, DAG/exit/live violations)
- T2 Dedupe search — existing issues by initiative label (read-only)
- T3 Present seed plan — EPIC + waves + preserved TASK metadata summary, board name/URL, create vs existing; ask for authorization
- 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
- 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
- Append/emit envelope from
prayog-skills/references/handoff-envelope.md. Stage id for this forge skill note:create-board-tickets(not a graph node). - Dual-write
handoff_pathwhen bound. - After successful seed, programme continues per pin
(
board-tickets-actionpass→wave-in-progress-action→pre-implement). Do not invent graph edges. - Honor pin
requiresonboard-tickets-action(spec merged, plan current,workmanifest-contract-pass).
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
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.

