원클릭으로 Manus에서 모든 스킬 실행

시작하기

backlog-execute

스타3

포크0

업데이트2026년 7월 14일 17:59

Autonomous execution skill for tickets (backlog). Use when implementing a ticket (TASK-xxx).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jeffutter

jeffutter/nixpkgs

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

SKILL.md

readonly

name	backlog-execute
description	Autonomous execution skill for tickets (backlog). Use when implementing a ticket (TASK-xxx).

Execute one ticket: $0

Instructions:

View the task: backlog task $0 --plain
Claim the task (if not already In Progress): backlog task edit $0 -s "In Progress" -a @ralph
Execute the work described in the task and its acceptance criteria
If you discover new work, create a follow-up ticket. If that follow-up blocks the current ticket (i.e., $0 cannot proceed until the new ticket is done), revert $0 back to To Do so it is not treated as actively in progress: backlog task edit $0 -s "To Do", then exit — do not continue executing a blocked ticket.
Mark acceptance criteria complete as you go
Add implementation notes: backlog task edit $0 --append-notes "..."
Add a final summary: backlog task edit $0 --final-summary "..."
Commit ALL changes (this is mandatory — never skip the commit step). Do this BEFORE marking the ticket Done — see step 10 for why: a. If you made changes inside sportsbook-bff/: cd into it, stage the changed files, and commit there FIRST (the pre-commit hook must pass). b. If you made changes inside penn-core/: cd into it, stage the changed files, and commit there FIRST. c. Back in the root repo, stage any changed files (including submodule pointer updates for sportsbook-bff and/or penn-core if you committed inside them, plus backlog task files). Commit with an informative but concise message. d. All commits must include the Co-Authored-By trailer.
Mark the ticket done: backlog task edit $0 -s Done
Fold that status change into the commit from step 8 instead of leaving it separate: stage the updated ticket file and git commit --amend --no-edit. Committing the code first and folding the Done flip in afterward means an interruption between steps 8-10 (e.g. this process being killed) never leaves a ticket marked Done with its work uncommitted — worst case is a ticket that's already-committed but still shows its prior status, which a future run can safely re-check rather than silently losing finished work.
Print a summary of what you did and exit

Do NOT start work on multiple tickets. Complete exactly ONE ticket then exit.

Additional Information: $ARGUMENTS

이 저장소의 다른 Skills

같은 저장소

review-pi-work

jeffutter/nixpkgs

Audit the last N completed backlog tickets that the autonomous `pi` loop finished, judging the work on Correctness, Conciseness, Clarity, Organization, and Resilience. File any required fixes as tightly-scoped backlog tickets with thorough plans and proper dependencies so the next `pi` round course-corrects. Invoke when checking in on pi's progress, e.g. "review pi's last few tickets".

2026-07-153

actual-cli

jeffutter/nixpkgs

Use when querying, managing, or automating Actual Budget via the command line — accounts, transactions, budgets, categories, payees, schedules, rules, or AQL queries against an Actual Budget server.

2026-04-243

acli

jeffutter/nixpkgs

Use acli CLI for Atlassian operations — primarily Jira work item management, project operations, sprint tracking, and board management with JQL search. Also covers Confluence page/space/blog operations and a CQL search fallback (acli has no native Confluence search).

2026-04-213

backlog-planner

jeffutter/nixpkgs

Autonomous planning skill for tickets (backlog). Use when planning implementation for a ticket (TASK-xxx). Spawns research subagents, analyzes dependencies, creates sub-tickets for discrete work, and writes detailed implementation plans.

2026-04-203

voice-dna

jeffutter/nixpkgs

Write or rewrite content in my authentic voice using my voice DNA profile. Use when drafting technical docs, blog posts, RFCs, proposals, or reviewing/editing prose for voice consistency.

2026-02-113

elixir

jeffutter/nixpkgs

Guidelines and best practices when writing Elixir code. Claude should use this skill whenever asked to modify, evaluate or review Elixir files (.ex or .exs).

2026-01-293

name	backlog-execute
description	Autonomous execution skill for tickets (backlog). Use when implementing a ticket (TASK-xxx).

Execute one ticket: $0

Instructions:

View the task: backlog task $0 --plain
Claim the task (if not already In Progress): backlog task edit $0 -s "In Progress" -a @ralph
Execute the work described in the task and its acceptance criteria
If you discover new work, create a follow-up ticket. If that follow-up blocks the current ticket (i.e., $0 cannot proceed until the new ticket is done), revert $0 back to To Do so it is not treated as actively in progress: backlog task edit $0 -s "To Do", then exit — do not continue executing a blocked ticket.
Mark acceptance criteria complete as you go
Add implementation notes: backlog task edit $0 --append-notes "..."
Add a final summary: backlog task edit $0 --final-summary "..."
Commit ALL changes (this is mandatory — never skip the commit step). Do this BEFORE marking the ticket Done — see step 10 for why: a. If you made changes inside sportsbook-bff/: cd into it, stage the changed files, and commit there FIRST (the pre-commit hook must pass). b. If you made changes inside penn-core/: cd into it, stage the changed files, and commit there FIRST. c. Back in the root repo, stage any changed files (including submodule pointer updates for sportsbook-bff and/or penn-core if you committed inside them, plus backlog task files). Commit with an informative but concise message. d. All commits must include the Co-Authored-By trailer.
Mark the ticket done: backlog task edit $0 -s Done
Fold that status change into the commit from step 8 instead of leaving it separate: stage the updated ticket file and git commit --amend --no-edit. Committing the code first and folding the Done flip in afterward means an interruption between steps 8-10 (e.g. this process being killed) never leaves a ticket marked Done with its work uncommitted — worst case is a ticket that's already-committed but still shows its prior status, which a future run can safely re-check rather than silently losing finished work.
Print a summary of what you did and exit

Do NOT start work on multiple tickets. Complete exactly ONE ticket then exit.

Additional Information: $ARGUMENTS