dev-workflow
Task-driven development workflow with TODO tracking. Use when user says "dev", "dev-workflow", or asks to work on tasks, develop features, or proceed with implementation.
When & Why to Use This Skill
This Claude skill implements a comprehensive, task-driven development workflow designed to streamline software engineering processes. It automates the transition from task identification to final implementation using a structured three-phase approach: Setup, Implementation, and Wrap-up. By integrating real-time TODO tracking, git-crew task management, and automated CI/CD verification via mise, it ensures developers maintain high code quality, consistent documentation, and efficient project progression with minimal manual overhead.
Use Cases
- Automated Feature Development: Streamline the creation of new features by automatically managing git branches, tracking incremental progress through granular TODOs, and ensuring all implementation steps are verified.
- Standardized Project Onboarding: Quickly gain context on unfamiliar codebases by following a mandatory documentation review and architecture analysis phase before starting any code modifications.
- Continuous Quality Enforcement: Maintain high engineering standards by integrating mandatory CI checks and test coverage analysis directly into the development lifecycle.
- Structured Task Management: Utilize git-crew integration to list, track, and complete tasks within the AI environment, reducing context switching and improving focus.
- Automated Reporting and Retrospectives: Generate detailed summary reports, technical findings, and design feedback automatically upon task completion to improve team communication.
| name | dev-workflow |
|---|---|
| description | Task-driven development workflow with TODO tracking. Use when user says "dev", "dev-workflow", or asks to work on tasks, develop features, or proceed with implementation. |
Dev Workflow
Implements the Development Flow from AGENTS.md with detailed steps and TODO tracking.
Auto-Start
When this skill is loaded, IMMEDIATELY begin Phase 1. Do NOT wait for user confirmation.
TODOs
Register ALL TODOs at once when starting Phase 1:
# Phase 1: Setup
- [ ] Read docs/README.md, core-concepts.md, architecture.md
- [ ] Check current task with `crew list` and `crew show <id>`
- [ ] Ensure on feature branch
# Phase 2: Implementation
- [ ] Plan implementation and update TODOs (add specific steps here)
# Phase 3: Wrap-up
- [ ] Run final CI check
- [ ] Check test coverage for new code
- [ ] Commit changes (no user confirmation needed)
- [ ] Run `crew complete <id>` to merge and close task
- [ ] Summary report (findings, retrospective)
Rules
- Start immediately - Begin Phase 1 upon skill load
- Register ALL TODOs at once - Include all phases when starting Phase 1
- Update TODOs in real-time - Mark in_progress/completed as you work
- One item in progress at a time - Focus and complete before moving on
- Add implementation steps - When reaching "Plan implementation and update TODOs", add specific steps
Reference: Phase Details
Phase 1: Setup
Goal: Understand context and prepare workspace.
Read project docs (skip if already familiar from this session)
- MUST read ALL docs:
- docs/README.md - Project overview
- docs/core-concepts.md - Design principles
- docs/architecture.md - Code structure
- MUST read ALL docs:
Check current task
- MUST execute
crew listto see all tasks - MUST execute
crew show <id>to view task details - If
crewis not available or returns error, ask the user which task to work on - Do NOT look for TASKS.md - this project uses git-crew for task management
- MUST execute
Ensure feature branch
- Check current branch:
git branch --show-current - If on
main: create feature branchgit checkout -b feature/<task-description> - If already on
feature/*: continue on current branch
- Check current branch:
Phase 2: Implementation
Goal: Complete the task with quality.
Plan implementation
- Break down the task into specific TODOs
- Each TODO should be a single, verifiable step
Implement incrementally
- Work on ONE TODO at a time
- Mark TODO as
in_progresswhen starting - Mark TODO as
completedimmediately when done
Run CI frequently
- Run
mise run ciafter significant changes - Fix any issues before proceeding
- Run
Update task status
- Use
crew edit <id> --status <status>to update task status as you progress
- Use
Phase 3: Wrap-up
Goal: Finalize changes and reflect on the session.
Final CI check
- Run
mise run cione last time - Ensure all tests pass
- Run
Check test coverage
- Run
mise run test:cover - Review coverage:
go tool cover -func=coverage.out | grep -E "(total|<new-package>)" - Add tests if coverage is insufficient
- Run
Commit changes (no user confirmation needed)
- Stage and commit with clear message
- Follow commit message format from AGENTS.md
Complete task
- Run
crew complete <id>to merge to main and close task
- Run
Summary report
- Output a consolidated report with the following sections:
## Summary ### What was done - Brief description of implemented changes ### Technical findings (if any) - Concerns, ambiguities, or potential issues discovered - Spec interpretation questions - Edge cases not covered by specs - Design decisions that might need confirmation ### Retrospective (if any) - Patterns suggesting AGENTS.md or docs/ improvements - Friction with specs in docs/ → append to DESIGN_FEEDBACK.md