agentleFS
Jamie-BitFlightJamie-BitFlight/claude_skills/.cursor/rules/backlog-before-work.mdc

claude_skills / rules

Cursor rule67 starsChanged 50 days agoMITView on GitHub

When you identify work needs multiple steps/jobs, create backlog items — don't just describe them

The file

We split this backlog-before-work.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you identify that work will need multiple steps or jobs: create backlog items for them — don't just describe them.

    line 8

≈ “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
backlog-before-work.mdc
---
description: When you identify work needs multiple steps/jobs, create backlog items — don't just describe them
alwaysApply: true
---

# Backlog Before Work

When you identify that work will need multiple steps or jobs: create backlog items for them — don't just describe them.

1. **Create or match a backlog item** — Use `work-backlog-item create` or `work-backlog-item` before starting.
2. **Plan** — When writing a plan, add it to the item via `mcp__plugin_dh_backlog__backlog_update(selector="{title}", plan="{path}")`.
3. **Progress** — When completing actions, update the task/plan artifact so progression is visible.

Skip only for trivial single-step requests (typos, one-off questions, immediate one-action fixes).

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.