본문으로 건너뛰기
cccskills
무료GitHub에 공개

gsd-review-backlog

Reviews deferred project tasks alongside their descriptions and supporting files, then lets users promote, keep, or remove each item. Promoted tasks join the active milestone with updated phase numbers and roadmap entries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Review and promote backlog items to active milestone

설치 방법 보기

이럴 때 유용합니다

  • Review deferred tasks and their supporting materials
  • Move selected backlog items into the active milestone
  • Remove outdated backlog items
  • Update roadmap entries and phase numbers

포함된 파일(1)

  • SKILL.md4.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

<objective> Review all 999.x backlog items and optionally promote them into the active milestone sequence or remove stale entries. </objective> <process>
  1. List backlog items:

    _BACKLOG=( .planning/phases/999* )
    if [ -e "${_BACKLOG[0]}" ]; then ls -d "${_BACKLOG[@]}"; else echo "No backlog items found"; fi
    
  2. Read ROADMAP.md and extract all 999.x phase entries:

    cat .planning/ROADMAP.md
    

    Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.

  3. Present the list to the user via AskUserQuestion:

    • For each backlog item, show: phase number, description, accumulated artifacts
    • Options per item: Promote (move to active), Keep (leave in backlog), Remove (delete)
  4. For items to PROMOTE:

    • Find the next sequential phase number in the active milestone
    • Rename the directory from 999.x-slug to {new_num}-slug:

_GSD_SHIM_NAME="gsd-tools.cjs"; _GSD_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; GSD_TOOLS="${_GSD_RUNTIME_ROOT}/gsd-core/bin/${_GSD_SHIM_NAME}"; _gsd_at() { for _p; do if [ -f "$_p" ]; then GSD_TOOLS="$_p"; return 0; fi; done; return 1; }; _gsd_id_ok() { case "$("$1" runtime-identity --raw 2>/dev/null || true)" in '{"packageName":"@opengsd/gsd-core"'*'}') return 0;; ) return 1;; esac; }; _gsd_homes() { set -- "${CLAUDE_CONFIG_DIR:-$HOME/.claude}" "${ANTIGRAVITY_CONFIG_DIR:-$HOME/.gemini/antigravity}" "$HOME/.gemini/antigravity-ide" "$HOME/.gemini/antigravity-cli" "${AUGMENT_CONFIG_DIR:-$HOME/.augment}" "${CLINE_CONFIG_DIR:-$HOME/.cline}" "${CODEBUDDY_CONFIG_DIR:-$HOME/.codebuddy}" "${CODEX_HOME:-$HOME/.codex}" "${COPILOT_CONFIG_DIR:-${COPILOT_HOME:-$HOME/.copilot}}" "${CURSOR_CONFIG_DIR:-$HOME/.cursor}" "${HERMES_HOME:-$HOME/.hermes}" "${KILO_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/kilo}" "${KIMI_CONFIG_DIR:-$HOME/.config/agents}" "$HOME/.agents" "${KIMI_CODE_HOME:-$HOME/.kimi-code}" "${OPENCODE_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/opencode}" "${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}" "${QWEN_CONFIG_DIR:-$HOME/.qwen}" "${TRAE_CONFIG_DIR:-$HOME/.trae}" "${WINDSURF_CONFIG_DIR:-$HOME/.codeium/windsurf}" "${ZCODE_CONFIG_DIR:-$HOME/.zcode}" "${GROK_AGENTS_HOME:-$HOME/.agents}"; for _h; do _gsd_at "$_h/gsd-core/bin/${_GSD_SHIM_NAME}" && return 0; done; return 1; }; if _gsd_at "${_GSD_RUNTIME_ROOT}/gsd-core/bin/${_GSD_SHIM_NAME}" "${_GSD_RUNTIME_ROOT}/.claude/gsd-core/bin/${_GSD_SHIM_NAME}" "${_GSD_RUNTIME_ROOT}/.codex/gsd-core/bin/${_GSD_SHIM_NAME}"; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif _gsd_homes; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif unset -f gsd_run; _G="$(command -v gsd_run)"; [ -n "$_G" ] && _gsd_id_ok "$_G"; then GSD_TOOLS="$_G"; gsd_run() { "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and no identity-proving gsd_run is on PATH. Run: npx -y @opengsd/gsd-core@latest --claude --local" >&2; exit 1; fi; GSD_IDENTITY_STATUS=unverified; _gsd_id_ok gsd_run && GSD_IDENTITY_STATUS=ok; export GSD_IDENTITY_STATUS; [ "$GSD_IDENTITY_STATUS" = ok ] || echo "WARNING: "$GSD_TOOLS" did not prove it is @opengsd/gsd-core - it is either a different package or an @opengsd/gsd-core older than the runtime-identity verb. See docs/how-to/diagnose-a-foreign-gsd-tools.md" >&2; if [ -n "${CLAUDE_ENV_FILE:-}" ] && [ -n "${GSD_TOOLS:-}" ]; then printf "export PATH='%s':"$PATH"\n" "${GSD_TOOLS%/}" >> "$CLAUDE_ENV_FILE" 2>/dev/null || true; fi NEW_NUM=$(gsd_run query phase.add "${DESCRIPTION}" --raw) ```

  • Move accumulated artifacts to the new phase directory
  • Update ROADMAP.md: move the entry from ## Backlog section to the active phase list
  • Remove (BACKLOG) marker
  • Add appropriate **Depends on:** field
  1. For items to REMOVE:

    • Delete the phase directory
    • Remove the entry from ROADMAP.md ## Backlog section
  2. Commit changes:

    gsd_run query commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md
    
  3. Report summary:

    ## 📋 Backlog Review Complete
    
    Promoted: {list of promoted items with new phase numbers}
    Kept: {list of items remaining in backlog}
    Removed: {list of deleted items}
    
</process>

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Add tests to a completed development phase using its records and implementation. Review the proposed coverage, then generate unit tests for individual components and browser tests for full workflows, verify them, and commit the test files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding automated tests after a development phase is complete
  • Turning acceptance criteria into test coverage
  • Reviewing which code needs unit or browser tests
open-gsd/gsd-core1.1만2026년 10월 18일 업데이트

Prepare an AI-SPEC.md design agreement for an AI development phase. The skill coordinates framework selection, documentation and domain research, and evaluation planning so the phase has a defined technical direction and assessment strategy.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Define the design agreement for an AI development phase
  • Research frameworks, documentation, and the application domain
  • Plan how to evaluate an AI system
open-gsd/gsd-core1.1만2026년 10월 18일 업데이트

Run an audit, separate findings that can be fixed automatically from those needing manual work, and apply eligible fixes with tests and separate commits. Use severity filters, a finding limit, or a classification-only dry run.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Fixing audit findings with test verification
  • Prioritizing findings by severity
  • Limiting how many findings are fixed
open-gsd/gsd-core1.1만2026년 10월 18일 업데이트

Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking completion criteria before archiving a milestone
  • Reviewing coverage of milestone requirements
  • Checking connections and user flows across phases
open-gsd/gsd-core1.1만2026년 10월 18일 업데이트

Audit acceptance tests, which check whether features meet user needs, and verification records across project phases. Compare outstanding items with the codebase, flag outdated documentation, and produce a prioritized plan for human testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Finding outstanding acceptance tests across phases
  • Collecting blocked items and checks needing human input
  • Checking whether verification records match the code
open-gsd/gsd-core1.1만2026년 10월 18일 업데이트

Run remaining GSD project phases through discussion, planning, and execution, while recording progress and phase documents. You can limit the phase range or keep decisions interactive; after all phases finish, the workflow audits and closes the milestone.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Running all remaining milestone phases
  • Executing a selected phase or range of phases
  • Answering discussion questions before background execution
open-gsd/gsd-core1.1만2026년 10월 18일 업데이트

open-gsd의 스킬 모두 보기

이 스킬의 문제 신고