What is project-management?

A set of project-management rules for organizing software work from initial building through ongoing maintenance. It defines a documentation layout and a story-based workflow, where stories are small pieces of work.

Use it to structure project documentation, create and complete stories, manage feature work, and track bug fixes or improvements.

It gives the coding agent a consistent way to plan work, track progress, and keep project documents organized. This reduces confusion about where requirements, designs, and task details belong.

project-management — Cursor rule for Cursor by copperdogma

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.

Clone the repo

git clone --depth 1 https://github.com/copperdogma/cursor-project-bootstrapper

Made for: Cursor.

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/rules/copperdogma/cursor-project-bootstrapper/project-management/github.svg)](https://agentmods.dev/rules/copperdogma/cursor-project-bootstrapper/project-management)

Your own site

<a href="https://agentmods.dev/rules/copperdogma/cursor-project-bootstrapper/project-management"><img src="https://agentmods.dev/badge/rules/copperdogma/cursor-project-bootstrapper/project-management/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/rules/copperdogma/cursor-project-bootstrapper/project-management"><img src="https://agentmods.dev/badge/rules/copperdogma/cursor-project-bootstrapper/project-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 852 This file is loaded in full into every session.

When invoked 852 The same file — it is already loaded in full.

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.00852	$0.00852
Opus 5.5	$0.00341	$0.00341
Sonnet 5.5	$0.00170	$0.00170
Haiku 4.5	$0.00085	$0.00085

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

Security

Grade A, and why

project-management 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.

bootstrapping/project-types/programming/work/project-management.mdc · 88 lines

How it starts

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

Programming Project Management

Overview

This file provides guidance for managing projects starting from the Building phase, after the project type is selected, and continuing into the Maintenance phase.

This document is used to guide project planning, management, and execution.

Phases

Building: Implement features and functionality through stories.
Maintenance: Manage updates, bug fixes, and improvements.

File Layout

/docs:
- requirements.md: Defines project requirements. Formatting guidelines in /docs/templates/requirements-template.md
- design.md: Outlines design details. Formatting guidelines in /docs/templates/design-template.md
- architecture.md: Specifies architectural guidelines. Formatting guidelines in /docs/templates/design-architecture.md
- stories.md: Lists all stories with IDs, titles, statuses, and links. Formatting guidelines in /docs/templates/design-stories.md
- /docs/stories/: Contains individual story files.
/docs/templates/:
- story-template.md: Template for new story files.
- stories-template.md: Template for maintaining /docs/stories.md.

Workflow

Building Phase

Story Management:
- Create new stories in /docs/stories/ using /docs/templates/story-template.md.
- Add each story to /docs/stories.md with a unique ID, title, status, and link.
- Update statuses in /docs/stories.md as work progresses (e.g., "In Progress," "Done").
- Use the build-story.md command to work on stories - it maintains work logs within story files for complete implementation history.
Implementation:
- Write code following /docs/architecture.md, /docs/design.md, and @requirements.md.
Progress Tracking:
- Log detailed implementation history in story work logs (see build-story.md command).
- Check docs/stories.md to identify the current active story (status: "In Progress").
- Review the active story's work log for current task, progress, and blockers.
- Reflect status changes in /docs/stories.md.
Completion:
- Test the implementation (e.g., run code, verify functionality).
- Update the story file with final notes in the work log section.
- Mark the story as "Done" in /docs/stories.md.
- Confirm completion with the user and suggest the next story or phase transition.

Read the full file on GitHub · 88 lines

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 · 88 lines · 852 tokens per session scan A f692c8b2e684

Subscribe to this mod's changes

project-management is a cursor rule published in the GitHub repository copperdogma/cursor-project-bootstrapper (4 stars, last pushed 11mo ago), licensed MIT. It adds 852 tokens to every session, about $0.0034 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.

Planning Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

project-management