agentsclimarketplace
Sign in

Case 04876

Skill knownasnaffy/prompthound/dataset/case_04876

Install and enforce a lightweight product-management workflow inside a code repo: feature-as-kanban boards, ROADMAP status tracking, branch/PR conventions, and an optional daily OpenClaw cron PM review. Use this skill when (1) starting work in a NEW repository/project that does not yet have a ROADMAP+feature-KANBAN system, (2) you are delegated to spin up a new project and want multi-agent coordination from day one, or (3) you are asked to fix/restructure an existing repo and introduce an organized backlog/feature tracking system. Also use when adding a daily PM audit loop (cron) to keep code + docs + PRs in sync.From its SKILL.md

Install
npx -y skills add knownasnaffy/prompthound --skill case_04876

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 587 tokens by cl100k_base, as published. Nobody here has run it

Repo Kanban PM System

What this skill does

Sets up a multi-agent-safe product workflow in a repo:

  • docs/roadmap/ROADMAP.md as the portfolio status
  • docs/features/<feature>/KANBAN.md as execution boards
  • docs/pm/bugs/ as the bug intake + triage inbox (linkable into KANBAN)
  • Updates AGENTS.md to enforce the workflow
  • (Optional) creates a daily OpenClaw cron job to run a PM review (includes bug triage)

When to use this skill (decision rule)

Use repo-kanban-pm when you are tasked with either:

  1. Creating/spinning up a new project/repo and multiple agents will work on it (or you want to avoid chaos later).

    • Goal: install ROADMAP + per-feature KANBAN boards immediately.

  2. Entering an existing repo to fix, refactor, or restructure it and it does not have a clear feature/backlog tracking system.

    • Goal: introduce the kanban workflow so subsequent work is trackable and PRs stay aligned.

Do not use this skill if the repo already has an equivalent system that the team actively uses (avoid duplicating governance).

Quick start

1) Initialize the repo workflow

Run:

bash scripts/init_repo_pm.sh /absolute/path/to/repo

This will:

  • create docs/pm/ with the workflow doc + template
  • create docs/pm/bugs/ with bug README + template
  • add KANBAN.md to any existing docs/features/*/ folders
  • patch AGENTS.md to include the kanban rules (idempotent)

2) Add a daily PM cron (optional)

Run:

bash scripts/add_daily_pm_cron.sh /absolute/path/to/repo --agent persey --tz Europe/Minsk --time 10:00

Operating rules (agents)

  1. Pick a feature from docs/roadmap/ROADMAP.md
  2. Create/update docs/features/<feature>/KANBAN.md and set status to in-progress
  3. Create a branch: feat/<feature-slug>-<short>
  4. PR must link the feature’s KANBAN.md
  5. On merge: mark KANBAN.md as done and tick the ROADMAP checkbox

Templates

  • Workflow spec: docs/pm/KANBAN-SYSTEM.md
  • Feature template: docs/pm/FEATURE-KANBAN-TEMPLATE.md

Notes

  • Keep KANBAN boards short.
  • ROADMAP contains status only; do not duplicate per-task detail there.

What ships with it: 2 files

4.3 KB alongside SKILL.md, 2 of them executable

scripts/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.