What is create-board-tickets?

A guarded workflow that creates programme engineering-board tickets from the work plan after a specification pull request has been merged.

Creating an epic and grouped wave of engineering issues from an approved implementation plan. It does not write product code.

It prevents tickets from being created before the required plan, merge checks, and board connection are confirmed.

create-board-tickets — Skill for Claude Code by drivestream-lab

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add drivestream-lab/prayog-skills --skill create-board-tickets

Clone the repo

git clone --depth 1 https://github.com/drivestream-lab/prayog-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/create-board-tickets/github.svg)](https://agentmods.dev/skills/drivestream-lab/prayog-skills/create-board-tickets)

Your own site

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/create-board-tickets"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/create-board-tickets/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/create-board-tickets"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/create-board-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,476 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00080	$0.01476
Opus 5.5	$0.00032	$0.00590
Sonnet 5.5	$0.00016	$0.00295
Haiku 4.5	$0.00008	$0.00148

Measured 2mo ago against content hash 01fc0d4e3bc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-board-tickets scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/forge/create-board-tickets/SKILL.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.yaml or references/layout-defaults.md.
Spec merge gate first — merged Implementation-Plan-{initiative}.md on integration branch; closed spec PR had spec-lgtm on 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, run launchpad board-bind --client <id> and stop. Governance wins over plan §9 target.project free text.
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.
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.
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.
Ids: prayog-skills/references/id-conventions.md. Paths: prayog-skills/references/artifact-write-contract.md. Checks: B1–B8.

Read the full file on GitHub · 115 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 115 lines · 80 tokens per session scan A 01fc0d4e3bc2

Subscribe to this mod's changes

create-board-tickets is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,476 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens