47 lines
1.4 KiB
Markdown
47 lines
1.4 KiB
Markdown
---
|
|
name: dev-workflow
|
|
description: Personal development workflow for software projects.
|
|
---
|
|
|
|
# Dev Workflow
|
|
|
|
This skill enforces my personal development workflow for software projects.
|
|
|
|
## Branch Strategy
|
|
|
|
- **Main branch**: `master` or `main` (production)
|
|
- **Development**: Always on feature branches off main
|
|
- **New work**: Features, fixes, and chores each get their own branch
|
|
|
|
## Workflow
|
|
|
|
### 1. Research / Discussion / Plan
|
|
|
|
Discuss the task, idea, or bug with the coding agent. The outcome is an **implementation plan** that includes:
|
|
|
|
- Summary of research and discussion
|
|
- Implementation plan broken into discrete steps
|
|
|
|
Save the plan in the feature branch as `{feature-slug}-plan.md`. The file is deleted when the workflow completes.
|
|
|
|
### 2. Implementation
|
|
|
|
Before starting, the agent reads `AGENT.md` (project guidelines). Implementation proceeds step-by-step according to the plan. Each step is committed individually.
|
|
|
|
### 3. Review
|
|
|
|
After implementation is complete, a subagent with **fresh context** reviews the code and implementation using `honest-reviewer`.
|
|
|
|
### 4. Iteration
|
|
|
|
The agent answers the reviewer's questions and fixes any issues. This cycle continues until the reviewer subagent approves.
|
|
|
|
### 5. Merge Request
|
|
|
|
Create an MR/PR and inform the user.
|
|
|
|
## Language Rule
|
|
|
|
- **Plans and artifacts**: Always in **English**
|
|
- **User discussions**: Any language
|