Skip to content
Skills Library
Management & product · Writing

project-docs

/project-docs

Use whenever creating or updating anything in docs/ of this project — a new feature, task, issue or report, changing any status, finishing a phase, or logging a decision. Defines file naming, numbering, required frontmatter and allowed status transitions; new feature requests follow adding-a-feature.md.

Licence
MIT
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use whenever creating or updating anything in docs/ of this project — a new feature, task, issue or report, changing any status, finishing a phase, or logging a decision. Defines file naming, numbering, required frontmatter and allowed status transitions; new feature requests follow adding-a-feature.md.

Original author description

Use whenever creating or updating anything in docs/ of this project — a new feature, task, issue or report, changing any status, finishing a phase, or logging a decision. Defines file naming, numbering, required frontmatter and allowed status transitions; new feature requests follow adding-a-feature.md.

How it works

  1. File naming
  2. Next number
  3. Creating a document
  4. Adding a feature
  5. Required frontmatter
  6. Status transitions
  7. Reports
  8. Decisions
Original SKILL.md headings · 128 lines, 969 words
SKILL.md preview
---
name: project-docs
description: Use whenever creating or updating anything in docs/ of this project — a new feature, task, issue or report, changing any status, finishing a phase, or logging a decision. Defines file naming, numbering, required frontmatter and allowed status transitions; new feature requests follow adding-a-feature.md.
---

# Project Docs

Rules for every document under `docs/`. Templates are in `templates/` next to this file.
All documents are written in English.

## File naming

`docs/<kind>s/<kind>-<NNNN>-<kebab-topic>-<YYYY-MM-DD>.md`

- `<kind>`: `feature`, `task`, `issue` or `report`
- `<NNNN>`: 4-digit zero-padded run number, starting at `0001`
- `<kebab-topic>`: 2–5 lowercase English words, characters `[a-z0-9-]` only; delete any other character without replacing it (`CI/CD` → `cicd`); a hyphenated word keeps its hyphen and counts as one word (`Decide phase-1 features` → `decide-phase-1-features`)
- `<YYYY-MM-DD>`: creation date — never changes, even when the file is updated

Example: `docs/tasks/task-0007-add-login-form-2026-11-02.md`

## Next number

1. List the kind's folder: `ls docs/tasks/` (or `docs/features/`, `docs/issues/`, `docs/reports/`).
2. Take the highest `NNNN` among the `.md` files (ignore `.gitkeep` and anything else) and
   add 1. No `.md` files → `0001`.
3. Each kind has its own sequence. Numbers are never reused and files are never deleted —
   use `cancelled` / `wont-fix` instead.

## Creating a document

1. Copy the matching template from `templates/`.
2. Replace every `{{...}}`. For `{{NAME: instruction}}`, follow the instruction and write the
   result. No `{{` may remain.
3. `created` and `updated` = today. `id` = `<kind>-<NNNN>`, matching the file name.
4. The first `## Log` line is `- <date> created (<initial status>)`.

## Adding a feature

When the human asks for a new feature or more scope, at any time, follow
`adding-a-feature.md` next to this file. Never turn a feature request straight into tasks.

## Required frontmatter

| Kind | Keys |
|---|---|
| feature | id, title, status, phase, ticket, created, updated, related |
| task | id, title, status, feature, ticket, created, updated, related |
| issue | id, title, status, created, updated, related |
| report | id, title, status, period, created, updated |
| core doc (PROJECT, ROADMAP, STACK / METHODS / STYLE / RESOURCES, docs/design/ARCHITECTURE, DESIGN) | title, status, created, updated |

`phase` (feature): a phase id from `docs/ROADMAP.md`, `backlog` when not placed yet, or `none`
when the project has no roadmap.

`feature` (task): the id of the feature the task belongs to, or `none` (decisions, chores,
bug fixes). A task's phase is its feature's phase.

`related` is a list of ids, e.g. `[task-0003, issue-0001]`. Link both directions.

`ticket` is a tracker ticket id (e.g. `FBTB-123`), or `none` when the task is not linked.

## Status transitions

Change status only along these arrows. On every change: set `updated:` to today and append
`- <date> <old> → <new> — <short reason>` to the file's `## Log`.

**Feature**
- `proposed` → `approved` / `rejected` — **only the human decides**; say why when rejected
- `approved` → `in-progress` — when its first task leaves `todo`
- `in-progress` → `done` — only when every task with this `feature:` is `done` or
  `cancelled` and every acceptance box is ticked
- any status except `done` → `cancelled` — say why

**Task**
- `todo` → `in-progress`
- `in-progress` → `review`
- `review` → `done` — only when every acceptance-criteria box is ticked
- `review` → `in-progress` — changes needed
- `todo` / `in-progress` / `review` → `blocked` — say what blocks it; link the issue if any
- `blocked` → the status it had before
- any status except `done` → `cancelled` — say why

**Issue**
- `open` → `investigating` → `resolved`
- `open` / `investigating` → `wont-fix` — say why
- `resolved` → `open` — reopened

**Core doc**
- `draft` → `approved` — **only the human approves**
- `approved` → `outdated` — when reality no longer matches the doc
- `outdated` → `draft` — rewrite in progress
- Never edit a doc with `status: approved` without asking the human first.

**Phase** (the `- **Status:**` line of each phase in `docs/ROADMAP.md`)
- `planned` → `active` → `done`. Exactly one phase is `active`.
- Before marking a phase `done`, all its features must be `done` or `cancelled`. Then set
  the next phase to `active` and ask the human before creating tasks for its `approved`
  features.

**Report**
- `draft` → `final`

## Reports

A report covers the period since the previous report (or since kickoff). Collect: features and tasks moved
to `done`, tasks in progress, issues opened and resolved, decisions added to
`docs/decisions/` (rows in `docs/DECISIONS.md`), and next steps. Set `period: <start> to <end>`.

## Decisions

Whenever you choose between real alternatives, create `docs/decisions/D-NNNN-<slug>.md` from
`templates/decision.md` and add its row to the index table in `docs/DECISIONS.md`; set the
index's `updated:` to today whenever you add or change a row.
- `<slug>`: the first 1–6 words of the title, by the `<kebab-topic>` character rule above.
- Next id = highest `D-NNNN` in the index + 1, assigned at the moment you write the file. Never
  pre-assign a `D-NNNN` id in a task or elsewhere — write "add a decision (docs/decisions/)"
  instead.
- Never rewrite an old entry. A change is a new entry that lists the old id in `supersedes`;
  then add the new id to the old file's `superseded-by` (the only edit allowed in an old file)
  and update the old row's status in the index.
- A decision that adds a dependency or changes the stack also checks for matching Claude Code
  tools, following `finding-tools.md` next to this file, and adds the rows the user picks to
  `AGENTS.md` → Recommended tools, and to the `## Related tools` section of each project skill
  they apply to, in the same change.
- A decision that changes an earlier choice also updates, in the same change, every doc that
  still states the old choice (a stack table row, the summary in `AGENTS.md` or the project
  brief, architecture notes); a doc with `status: approved` needs the human's yes first.
- A decision that removes a technology lists that technology's rows in `AGENTS.md` →
  Recommended tools and its bullets in `## Related tools` sections, and removes each one only
  when the user says yes.
Files in this package (9)
  • KIT-VERSION 1 KB
  • SKILL.md 6 KB
  • adding-a-feature.md 5 KB
  • finding-tools.md 5 KB
  • templates/decision.md 1 KB
  • templates/feature.md 1 KB
  • templates/issue.md 1 KB
  • templates/report.md 1 KB
  • templates/task.md 1 KB

Versions

RepositoryScoreLicence
This page · DPatta/project-docs-kit100MIT
coco-research/coco100MIT
nasrulhazim/claude100MIT
event4u-app/agent-config100MIT
GGaryyy/POBG100MIT
DPatta/project-docs-kit100MIT
jezweb/claude-skills100MIT
waynesutton/builder-skills100Apache-2.0
xstongxue/best-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version ff6746a0628a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91ogt-docs-create-task
    Create and manage task documents in the docs/todo/ workflow. Use when creating new tasks, updating task status, or moving tasks between workflow stages. Provides complete task lifecycle management with verification.
  • 100project
    The project's plan, backlog, decisions and specifications, kept in markdown by deterministic commands. Use whenever the work adds, starts, finishes, postpones or reassigns a task, needs a task's, a decision's or a spec's number, looks a decision or a spec up or records a new…
  • 100project-tracker
    Track development work in the user's self-hosted Project Manager (projects with a Kanban board, epochs, folders/files, time tracking, architecture diagram, design docs). Use whenever the user asks for a new feature, content, bug fix or refactor; when starting or finishing…
  • 100manage-adr
    Create, update, and validate Architecture Decision Records (ADRs) following MADR 4.0 format. Use when the user mentions ADR, architecture decision, decision record, or asks to document a technical decision. Also use when creating new files in docs/decisions/. Handles numbering,…
  • 90pmo-kit
    Project standards and portfolio toolkit for any organisation running more than one project. Captures how the organisation runs projects in one standards sheet (project sizes, required documents, approval levels, status colour rules, risk scales, naming, reporting rhythm), then…
  • 90todo-report
    Generate an interactive HTML status page for the project at docs/status.html from TODO.md, CHANGELOG.md, git and the plan doc. Use for /todo-report. Shows KPIs, lanes with progress, the filterable task tree with Done when, links, state and blockers, release history, claims, test…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.