agentleFS
kunwarVivekkunwarVivek/mcp-github-project-manager/.cursor/rules/beads.mdc

mcp-github-project-manager / rules

Cursor rule105 starsChanged 51 days agoMITView on GitHub

This project uses Beads (bd) for issue tracking. Run bd prime to get complete workflow documentation in AI-optimized format. bd prime is the single source of truth for operational commands and session workflow. For detailed docs: see AGENTS.md, the beads quickstart (https://github.com/gastownhall/beads/blob/main/docs/getting-started/quickstart.md), or run bd --help

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this beads.mdc into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use bd ready to find available work

    line 15
  2. Very specific:

    Use bd create to track new issues/tasks/bugs

    line 16
  3. Distinctive:

    Treat commit, push, and Dolt remote sync as policy-controlled handoff actions

    line 17
  4. Very specific:

    Run bd prime for complete workflow context (SSOT for operational commands)

    line 18
  5. Very specific:

    Default to conservative git authority: report status and proposed commands unless the user, orchestrator, or repository profile explicitly …

    line 19
  6. Very specific:

    Check for ready work: bd ready

    line 37
  7. Very specific:

    Run bd prime to get complete workflow documentation in AI-optimized format.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
beads.mdc
---
alwaysApply: true
---

<!-- BEGIN BEADS INTEGRATION -->
<!-- Auto-generated by 'bd setup cursor'. Content between these markers is managed by bd. -->

# Beads Issue Tracking

This project uses [Beads (bd)](https://github.com/gastownhall/beads) for issue tracking.

## Core Rules

- Track ALL work in bd (never use markdown TODOs or comment-based task lists)
- Use `bd ready` to find available work
- Use `bd create` to track new issues/tasks/bugs
- Treat commit, push, and Dolt remote sync as policy-controlled handoff actions
- Run `bd prime` for complete workflow context (SSOT for operational commands)
- Default to conservative git authority: report status and proposed commands unless the user, orchestrator, or repository profile explicitly authorizes commit/sync/push

## Quick Reference

```bash
bd prime                              # Load complete workflow context (SSOT)
bd ready                              # Show issues ready to work (no blockers)
bd list --status=open                 # List all open issues
bd create "title" -t task -p 2        # Create new issue
bd update <id> --claim                # Claim work atomically
bd unclaim <id>                       # Release stuck issue (agent crashed)
bd close <id>                         # Mark complete
bd dep add <issue> <depends-on>       # Add dependency
bd dolt push                          # Sync with remote when authorized
```

## Workflow

1. Check for ready work: `bd ready`
2. Claim an issue atomically: `bd update <id> --claim`
3. Do the work
4. Mark complete: `bd close <id>`
5. Handoff: report changed files, validation, issue status, and any proposed commit/sync/push commands

## Issue Types

- `bug` - Something broken
- `feature` - New functionality
- `task` - Work item (tests, docs, refactoring)
- `epic` - Large feature with subtasks
- `chore` - Maintenance (dependencies, tooling)

## Priorities

- `0` - Critical (security, data loss, broken builds)
- `1` - High (major features, important bugs)
- `2` - Medium (default, nice-to-have)
- `3` - Low (polish, optimization)
- `4` - Backlog (future ideas)

## Context Loading

Run `bd prime` to get complete workflow documentation in AI-optimized format.
`bd prime` is the single source of truth for operational commands and session workflow.

For detailed docs: see AGENTS.md, the beads quickstart
(https://github.com/gastownhall/beads/blob/main/docs/getting-started/quickstart.md), or run `bd --help`

<!-- END BEADS INTEGRATION -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.