Senior Dev

Production development workflow with TODO tracking, Graphite PRs, GitHub issues, Vercel deploy checks, and SMS notifications. Use when starting a new task, fixing bugs, implementin…

michaelmonetized

@michaelmonetized

What This Skill Does

A 12-step production development workflow that integrates TODO tracking, Graphite PRs, GitHub issues, Vercel deploy checks, and SMS notifications. It guides the user from task setup through execution, code review, deployment monitoring, and cleanup.

Replaces manually tracking tasks across separate tools and remembering multi-step deployment procedures by providing a single, repeatable workflow with automated checks.

When to Use It

  • Start a new feature or bug fix with structured TODO tracking
  • Create a GitHub issue and link it to a Graphite PR for traceability
  • Monitor a Vercel deployment after merging a PR and auto-fetch logs on failure
  • Address code review feedback and update an existing PR with `gt modify`
  • Report task completion with PR URL and deploy status

Install

$ openclaw skills install @michaelmonetized/senior-dev

Senior Dev

A 12-step production workflow that keeps context across compaction.

Workflow

1. Setup

cd ~/Projects/<project>

Create or append to TODO.md:

## [Date] Task: <description>
- [ ] Subtask 1
- [ ] Subtask 2

2-3. Execute & Track

Complete work, check off TODO items as done.

Update CHANGELOG.md (create if missing):

## [Unreleased]
### Added/Changed/Fixed
- Description of change

4-5. Stage & Verify

git add -A
git diff --staged  # Verify changes match request

6-7. Create PR

Branch naming: (issue|feature|fix)/<short-description>

gt create "feature/add-dark-mode" -m "Add dark mode toggle"
gt submit

If this fixes an issue, create the issue first:

gh issue create --title "Bug: description" --body "Details..."
# Note the issue number
gt create "issue/42-fix-login-bug" -m "Fix login bug (#42)"
gt submit

8-9. Review Cycle

Wait for reviewer comments. Address feedback:

# Make fixes
git add -A
gt modify -m "Address review feedback"
gt submit

10-11. Post-Merge Deploy Check

After PR merges:

git checkout main && git pull

For Vercel projects:

# Watch deployment (polls until Ready/Error, auto-fetches logs on failure)
vl

If build fails → gh issue create with error logs, restart from step 6.

12. Report & Cleanup

Report completion format:

✅ [Project] Task completed PR: <url> Deploy: success/failed

Quick Reference

StepCommandPurpose
Stagegit add -AStage all changes
Verifygit diff --stagedReview before commit
Branchgt create "type/name" -m "msg"Create branch + commit
PRgt submitPush + create/update PR
Issuegh issue createTrack bugs/tasks
DeployvlWatch build, auto-fetch logs on error

Branch Prefixes

  • feature/ — New functionality
  • fix/ — Bug fixes
  • issue/ — Linked to GitHub issue (include #number)
  • chore/ — Maintenance, deps, config

Files to Maintain

  • TODO.md — Active task tracking (survives context compaction)
  • CHANGELOG.md — Version history
  • PLAN.md — Architecture decisions (optional)

Tools Required

  • gt — Graphite CLI for stacked PRs
  • gh — GitHub CLI for issues
  • vl — Vercel deploy watcher (or vercel CLI)

Top skills in this category