Skip to content

Consolidate skills into workon-flow and workon-delivery#2

Open
macrivello wants to merge 4 commits into
cli-commands-expansionfrom
consolidated-skills
Open

Consolidate skills into workon-flow and workon-delivery#2
macrivello wants to merge 4 commits into
cli-commands-expansionfrom
consolidated-skills

Conversation

@macrivello

Copy link
Copy Markdown
Owner

Summary

  • Replace 8 per-command skill files with 2 consolidated skills covering the full workflow
  • workon-flow: ticket discovery, validation, cross-repo orchestration, auto mode assessment
  • workon-delivery: PR lifecycle, CI monitoring, review handling, merge (with repo PR template injection)
  • Both skills include dynamic context injection (! blocks) for automatic session state
  • Auto mode support: tickets that pass deep validation can run the full pipeline with merge as the only human gate

Depends on

Test plan

  • Symlink ~/.claude/skills/workon-flow → repo skills/workon-flow/ and verify skill discovery
  • Symlink ~/.claude/skills/workon-delivery → repo skills/workon-delivery/ and verify skill discovery
  • Invoke workon-flow — verify dynamic context injection shows workflow state
  • Invoke workon-delivery — verify PR template injection from .github/PULL_REQUEST_TEMPLATE.md
  • Test auto mode assessment: workon validate <id> --deep --json → automatability report

🤖 Generated with Claude Code

@macrivello macrivello left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review findings at time of initial review. See inline comments on specific files for resolution status.

Critical

  1. Command duplicationcontext, cleanup, worktree in both skills
  2. Circular dependency — skills reference each other without documenting the pattern
  3. Missing error handling guidance — no guidance when CLI commands fail
  4. Test failure logic contradiction — mandatory gate vs stop condition overlap

Important

  1. Ambiguous auto mode for cross-repo — unclear if subtasks can run in auto mode
  2. Dangerous --yes in auto loops — no test verification before pushing

-agent:code-reviewer:claude-opus-4-6

macrivello and others added 4 commits February 9, 2026 20:24
Replace 8 per-command skill files with 2 consolidated skills that cover
the full workflow. Both skills include dynamic context injection for
session state, detailed workflow documentation, and auto mode support
for minimal-intervention execution on well-validated tickets.

workon-flow: ticket discovery, validation, cross-repo orchestration
workon-delivery: PR lifecycle, CI monitoring, review handling, merge

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…eview

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add worktree primitives so tickets can be offloaded to isolated directories
where background Claude agents run the full auto-mode pipeline, while the
main worktree stays free for interactive use.

New commands:
- workon worktree add <id>: create worktree + branch from base
- workon worktree list [--json]: show all worktrees with pipeline status
- workon worktree remove <id> [--keep]: remove worktree + branch
- workon worktree status [id]: detailed status view
- workon worktree update-status --stage <stage>: agent progress reporting
- workon start <id> --worktree: sugar for worktree add

Integration:
- cleanup: detects linked worktree, removes instead of branch delete
- context: shows "Background Work" section, flags blocked worktrees
- .gitignore: idempotently adds .worktrees/ and .workon-status.json

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove command duplication (cleanup from flow, context from delivery)
- Add companion skills note documenting intentional handoff pattern
- Add error handling guidance to both skills
- Clarify test failure logic (modified vs unmodified code)
- Clarify auto mode eligibility for cross-repo subtasks
- Add local test verification before --yes pushes in auto mode

Co-Authored-By: agent(claude-opus-4-6) <agent@noreply>
| `workon pr-push [pr-number] --yes` | Push changes + re-request review |
| `workon pr-ready [pr-number] --yes` | Mark draft PR as ready for review |
| `workon ci-status [branch]` | Check CircleCI status |
| `workon ci-failure [job-number]` | Get detailed CI failure output |

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cleanup command kept here in delivery (removed from flow). Context command removed from here (kept in flow). Worktree commands kept in flow only.


# Workon Flow

> **Note**: workon-flow and workon-delivery are companion skills. Flow handles ticket discovery through implementation; Delivery handles the PR lifecycle through merge. They hand off to each other at defined boundaries.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added companion skills note to document the intentional handoff pattern between flow and delivery.


See `commands-reference.md` for detailed flag reference.

## Error Handling

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added error handling guidance: retry once on network errors, report immediately on invalid IDs, never proceed if a step fails.

- **Max 3 CI fix attempts** — after 3 failures, stop and report to user
- **Review changes > 20 lines of rework** — if a reviewer requests large changes, stop and consult user
- **Scope creep detection** — if implementation requires changes outside what the ticket describes, stop
- **Test failures in unmodified code** — if tests you didn't write or modify are failing (flaky tests, environment issues), stop and report to user

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarified: this applies to tests in unmodified code only (flaky/environment). The mandatory test gate in step 4 handles failures in modified code.

- `ready: true` from deep validation
- No semantic findings with category `coverage-gap`, `contract-mismatch`, or `thin-subtask`
- No subtasks (single-repo ticket) — parent-level cross-repo orchestration requires guided mode
- Individual subtasks within a cross-repo ticket CAN run in auto mode if they independently pass auto-eligibility checks

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarified: parent-level cross-repo orchestration requires guided mode, but individual subtasks CAN run in auto mode independently.

In auto mode, CI fix is a loop with a retry limit:

1. `workon ci-status` — if green, move on
2. If red: `workon ci-failure` → diagnose → fix → **run tests locally to verify fix** → `workon pr-push --yes`

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added local test verification step before each --yes push in auto mode (both CI fix and review feedback loops).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant