agentleFS
Sign inStart free
lgzarturolgzarturo/codeconductor/.agents/skills/backlog/SKILL.md

backlog

Skill0 starsChanged 26 days agoMITView on GitHub

Guides agents through authoring BACKLOG.md and OpenSpec change folders. Use when running /cc-backlog or /cc:backlog, creating or appending backlog items, or preparing work for /cc-openspec. Delivery is skill openspec.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use issue, worktree and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    issue

    Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.

    Also in 3 projects that use this

  • MicrosoftSkill

    worktree

    Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 4 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Create or append BACKLOG.md, then openspec validate / plan.

    line 13
  2. Very specific:

    If graphify-out/graph.json exists, graphify query "<objectives>".

    line 24
  3. Very specific:

    Create BACKLOG.md from presets/templates/BACKLOG.md or append under ## Items.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “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
SKILL.md

Backlog authoring

Overview

Create or append BACKLOG.md, then openspec validate / plan. Do not deliver the item here.

When to Use

  • /cc-backlog, first backlog in a repo, or appending ### BC-xxx items

NOT for executing an item (openspec) or for scorecards (evaluation).

Process

  1. If graphify-out/graph.json exists, graphify query "<objectives>". Then repo-explorer. Scope names real files.
  2. Invoke task-coach. One grilling question per assumption. Reject vague acceptance ("improve UX"). At most 3 [NEEDS CLARIFICATION].
  3. ccep evaluate --command backlog. If stop, wait for the human.
  4. Create BACKLOG.md from presets/templates/BACKLOG.md or append under ## Items. Do not rewrite ## Global or ## Archive.
  5. Next ID = max numeric suffix in Items + Archive + 1, zero-padded (BC-013).
  6. npx cc-codeconductor openspec validate. Fix until valid.
  7. openspec plan BC-xxx for each new item this run. Then tell the user to run /cc-openspec.

Required sections: ## Global, ## Items, ## Archive. Each item: ### BC-001 | Title with Priority, Status (READY after grilling), Type, Depends on, Description, Scope, Out of scope, Acceptance.

Local artifacts (BACKLOG.md, openspec/, .codeconductor/openspec-state.json) are gitignored in consumer projects. Do not git add them.

Common Rationalizations

RationalizationReality
This fix is small; skip the Task CardEvery item needs measurable acceptance.
I'll validate laterDo not plan until openspec validate passes.
Archive can be rewrittenArchive is history. Never rewrite or re-execute.

Red Flags

  • Acceptance that cannot fail a check
  • Editing openspec-state.json by hand
  • Planning an invalid backlog

Verification

  • openspec validate exit 0
  • New items have FR/SC-ready measurable acceptance
  • User pointed at /cc-openspec for delivery

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.

Check your setup, free