Skip to content
cccskills
FreePublished on GitHub

add-backlog

Add an idea to the backlog parking lot (999.x numbering)

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<objective> Add a backlog item to the roadmap using 999.x numbering. Backlog items are unsequenced ideas outside the normal phase sequence. </objective> <process>
  1. Read ROADMAP.md to find existing backlog entries:

    cat .planning/ROADMAP.md
    
  2. Find next backlog number:

    NEXT=$(bm-sdk query phase.next-decimal 999 --raw)
    

    If no 999.x phases exist, start at 999.1.

  3. Add to ROADMAP.md under a ## Backlog section. If the section doesn't exist, create it at the end. Write the ROADMAP entry BEFORE creating the directory, so directory existence reliably means the phase is already registered (prevents false duplicate detection in hooks checking 999.x directories, #2280):

    ## Backlog
    
    ### Phase {NEXT}: {description} (BACKLOG)
    
    **Goal:** [Captured for future planning]
    **Requirements:** TBD
    **Plans:** 0 plans
    
    Plans:
    - [ ] TBD (promote with /gsd:review-backlog when ready)
    
  4. Create the phase directory:

    SLUG=$(bm-sdk query generate-slug "$ARGUMENTS" --raw)
    mkdir -p ".planning/phases/${NEXT}-${SLUG}"
    touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
    
  5. Commit:

    bm-sdk query commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" .planning/ROADMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
    
  6. Report:

    ## 📋 Backlog Item Added
    
    Phase {NEXT}: {description}
    Directory: .planning/phases/{NEXT}-{slug}/
    
    This item lives in the backlog parking lot.
    Use /gsd:discuss-phase {NEXT} to explore it further.
    Use /gsd:review-backlog to promote items to active milestone.
    
</process> <notes> - 999.x numbering keeps backlog items out of the active phase sequence - Phase directories are created immediately, so /gsd:discuss-phase and /gsd:plan-phase work on them - No `Depends on:` field — backlog items are unsequenced by definition - Sparse numbering is fine (999.1, 999.3) — always uses next-decimal </notes>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add phase to end of current milestone in roadmap

The English summary is being prepared. Showing the original description.

buildomator/buildomator92Updated Oct 17, 2026

Generate tests for a completed phase based on UAT criteria and implementation

The English summary is being prepared. Showing the original description.

buildomator/buildomator92Updated Oct 17, 2026

Capture idea or task as todo from current conversation context

The English summary is being prepared. Showing the original description.

buildomator/buildomator92Updated Oct 17, 2026

Generate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategy

The English summary is being prepared. Showing the original description.

buildomator/buildomator92Updated Oct 17, 2026

Analyze phase dependencies and suggest Depends on entries for ROADMAP.md

The English summary is being prepared. Showing the original description.

buildomator/buildomator92Updated Oct 17, 2026

Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit

The English summary is being prepared. Showing the original description.

buildomator/buildomator92Updated Oct 17, 2026

See all skills by buildomator

Report a problem with this skill