القائمة
Use when the user runs /galdr:backlog, or when a skill explicitly defers something to a later cycle — reviews, records, or resolves deferred work in docs/backlog.md, the pack's backlog file.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | backlog |
| description | Use when the user runs /galdr:backlog, or when a skill explicitly defers something to a later cycle — reviews, records, or resolves deferred work in docs/backlog.md, the pack's backlog file. |
Owns docs/backlog.md end to end: the entry format, the Open/Resolved structure, the
default list action, the append-on-defer rule other skills follow, and resolve. This
file is the single source of truth for all of that — no other skill restates the
format; they reference this one instead.
docs/backlog.md is the backlog — a fixed convention, like memory-progress.md:
always this path, never a per-repo setting (a configurable path is itself a deferred
backlog item, not solved here). It holds deferred work — parked ideas, findings not
fixed yet, and follow-ups — not a task list and not runtime state.
One bullet per item, carrying four fields: what, why, target, source.
- **<what>** (target <version/date>) — <why it was deferred, one or two sentences>.
Source: <where this came from — a spec section, a review finding, a conversation>.
Example:
- **Rate-limit bridge-installer** (target 0.4) — opt-in setup step so machines
without the statusline still get real usage %. Source: 0.3 shape.
All four fields are required. A bullet missing target or source is incomplete —
fill it in before appending rather than leaving it for later.
Two sections, always present, never fewer:
## Features / ideas (an existing heading recognized as Open); a fresh
backlog file uses the heading ## Open.## Resolved findings; a fresh file uses ## Resolved.A backlog may also carry other, older sections (for example a pre-convention "trial-era" dump). Leave those as found — they predate this structure and this skill does not rewrite them.
Never delete an item outright. A done item moves to Resolved with a note; nothing that was once tracked silently disappears.
/galdr:backlog with no argument lists the Open items only — name, target, and
the one-line why, in file order. Never include Resolved items in this listing: a user
asking what's in the backlog wants what's still outstanding, not the history.
This is the rule shape, plan, waves, branches, and review each reference
instead of restating. When one of those skills explicitly defers something to a later
cycle — not every passing idea, only a real "this waits" decision — it appends one
bullet to the Open section, in the exact entry format above. Nothing else changes: no
new section, no edit to neighboring bullets.
A user can also ask directly to add an item; the same format and the same rule apply.
When an open item's work lands, move it: remove its bullet from Open, and add one line under Resolved:
- **<what>** — RESOLVED <version/date>: <what changed, one line>.
Keep the bold <what> name so the item stays findable by name across both sections.
Resolve is explicit — nothing here auto-resolves an item; a skill or the user states
the work is done before the move happens.
Use once a spec is approved and ready to become an executable task list — turns spec requirements into a wave-based plan of write-scoped, testable tasks that waves can dispatch. Invoke via route or explicit command.
Use when a plan already exists and is ready to run — dispatches each wave's tasks, reviews every return before trusting it, and gates advancement on evidence. Invoke via route or explicit command.
Use when writing a new galdr skill, editing an existing one, or running the pack's quarterly prune review.
Continuation protocol for resuming work after a break, handing off to another session, a subagent, or Codex, and parking fast under a usage limit. Invoke via route or explicit command.
Use once per repo to create or refresh docs/agents/galdr.md — the config verify, waves, review, branches, and route read for gate commands, invariants, models, and smoke details. Slash-command only, not router- or model-invoked.
Use when the user runs /galdr:core to install, uninstall, or check galdr's core rules block on this machine for Claude, Codex, or Antigravity. Run install once per agent to write the marked block into that agent's rules file (or the Claude enabled flag); uninstall to remove it; status to report state without writing.