senior-dev

Manage development tasks through a 12-step workflow with TODO tracking and deployment checks.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/marcoamu/openclaw-workspace --skill senior-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-dev
Source: https://github.com/marcoamu/openclaw-workspace/tree/main/skills/senior-dev
Command: npx skills add https://github.com/marcoamu/openclaw-workspace --skill senior-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production development workflows with tracked progress for tasks, code reviews, and reliable releases.

Core Features & Use Cases

  • 12-step workflow to manage setup, execution, staging, PRs, reviews, and deployment checks.
  • Maintains context across compaction with TODO.md, CHANGELOG.md, and PLAN.md.
  • Supports team collaboration with Graphite (gt), GitHub (gh), and Vercel (vl) integrations for end-to-end delivery.
  • Example use: starting a new feature and tracking progress through to deployment.

Quick Start

Begin a new task by adding a TODO.md entry and follow the 12-step workflow to complete, review, and deploy.

Frequently Asked Questions about senior-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track development tasks from setup through deployment?

You can track development tasks end-to-end by following a structured 12-step workflow that enforces TODO tracking, changelog updates, PR reviews, and post-merge deployment checks for reliable releases.

How does context tracking work during long production workflows?

Context tracking across compaction works by maintaining TODO.md, CHANGELOG.md, and PLAN.md files throughout the development lifecycle to ensure progress and state are preserved.

Can I use GitHub and Vercel integrations for code review and deploy checks?

Yes, the workflow supports team collaboration using GitHub (gh) for PR reviews, Graphite (gt) for stacking, and Vercel (vl) for post-merge deployment checks.

What is the best way to start a new feature using a structured workflow?

The best way to start a new feature is by adding a TODO.md entry and following the 12-step workflow to systematically complete, review, and deploy the code.

Does this workflow support bug fixes and refactoring or just new features?

The workflow supports starting new features, bug fixes, and refactors within a team by applying the same production-grade process for tracking progress and deployment.

Why maintain a changelog during code review and PR management?

Maintaining a changelog during PR management ensures that all complex development work is documented, providing reliable release tracking and context across the team.