Skill Claude

Docs Project Management

docs-project-management/

2 views 0 downloads

Manage a whole project inside the repo's docs/ folder: roadmap, PRDs, epics, user stories, test cases and bugs as linked Markdown files with a status lifecycle. No issue tracker needed.

Docs Project Management: Brain Lab skill for Claude Code

Run an entire project from the repo's docs/ folder, no external issue tracker, no ticket system.

Why use it

Project state lives in a tracker the code doesn't know about, and the two drift apart the day after kickoff.
Agents invent their own folders, link wording and status values, so nothing cross-references.
"What was actually done?" has no answer that a reviewer can read in the diff.

What it does

The work-item taxonomy: roadmap → PRD → TRD → epics → user stories → test cases → bugs, each in its own docs/ folder.
The link graph as relative markdown links, user story part of epic, test case is tested by story, bug blocks story, PRD↔TRD.
The YAML-frontmatter status lifecycle + the bookend rule: move status: forward when you start, again when you finish.
The mandatory test-case template and the bug + RCA report format.
The team work-reporting convention: one session folder per run, every agent bookends a start/completion report there.

Benefits

Your tracker ships with your code. Work item = markdown file. Status = a diff. History = git.
Nothing drifts. Requirements, tests and bugs live next to what they describe.
Reviewable progress. "What got done?" is answered by the PR itself.
Still navigable at 300 files, because every agent writes to the same model.
Zero tooling cost. No tracker, no license, no sync job, day one of a new project.

Install

Download this skill and copy the docs-project-management folder to .claude/skills/docs-project-management/ in your project, or to ~/.claude/skills/docs-project-management/ to use it in every project. Claude Code finds it on its own; you can also call it with /docs-project-management.

Part of the Agent Engineering bundle. To get the whole set as a Claude Code plugin: /plugin marketplace add endorphin-ai/hasbrains-agent-kit, then /plugin install agent-engineering@hasbrains-agent-kit.

Source: endorphin-ai/hasbrains-agent-kit. License: MIT.

Files (16)

---
id: work-item-taxonomy
title: Work-Item Taxonomy (WHERE each item lives)
summary: The docs/ subfolder + filename pattern + owning role for every document type — Project brief, Project config, Roadmap, PRD, TRD, Epic, User Story, Bug, Test Case, Session reports, Feature log.
tags: [docs-pm/taxonomy, docs-pm/model]
load_when: When you need to know WHERE a work item lives, what to name its file, or which role owns it.
links: [[link-graph]], [[status-lifecycle]], [[conventions-recap]]
---

# Work-Item Taxonomy (WHERE each item lives)

TABLE taxonomy
  COLUMNS: Item, Location, Filename pattern, Owning role
  ROW: Project brief  | docs/project_brief.md | single file — the product spec, the SOURCE OF TRUTH  | PM / user
  ROW: Project config | docs/project_config/  | info.md — project facts agents read at runtime       | PM
  ROW: Epic           | docs/epics/           | <kebab-title>.md (e.g. membership-billing.md)        | PM
  ROW: Roadmap        | docs/ROADMAP.md (+ docs/roadmap.json cache) | single file + JSON mirror      | PM
  ROW: PRD            | docs/prd/             | <kebab-feature>-prd.md                               | PM
  ROW: TRD            | docs/trd/ (canonical home; + index.json registry, index.md) | <kebab-feature>-trd.md | Architect
  ROW: User Story     | docs/user_stories/    | NNN-<kebab-title>.md (e.g. 001-user-registration.md)| PM
  ROW: Bug            | docs/bugs/            | <kebab-summary>.md                                   | QA / security / reviewer (whoever finds it)
  ROW: Test Case      | docs/test_cases/      | tc-NNN-<kebab-behavior>.md                           | QA
  ROW: Session report | docs/sessions/<YYYY-MM-DD>-<slug>/ | README.md manifest + <phase-N>-<agent>.md per run | orchestrator creates; every agent reports
  ROW: Feature log    | docs/reports/         | feature-log.md (lean index) + feature-log/<slug>.md  | every agent appends its run-row

  RULES
    - Descriptive kebab-case filenames — NEVER opaque IDs. An external work-item ref (e.g.
      TICKET-<n>), when one exists, lives in frontmatter + the title line, not in the filename.
    - Every item is a committed markdown file with YAML frontmatter ([[status-lifecycle]]) + a body.
    - Each subfolder may carry a template_<type>.md seed; new items copy its shape.
    - TRD home = docs/trd/ (the single canonical TRD location — do NOT create a parallel
      docs/architecture/ folder). The architect MUST register every TRD it authors in
      docs/trd/index.json — a machine-readable registry (one entry per TRD: file, title, ref,
      milestone, status, related_prd) kept complete for future lookup — and refresh the human
      docs/trd/index.md row. index.json is the registry; index.md is the human index; both live
      alongside the TRD files.

> Relationships between these items are written as relative-markdown links — see [[link-graph]].
> Status is tracked in each file's frontmatter — see [[status-lifecycle]].