Feature Development Workflow

CRITICAL WARNING

THIS WORKFLOW IS MANDATORY. VIOLATION IS NOT ACCEPTABLE.

If you skip any step or write code before Step 3 is complete, you have FAILED. Follow the steps EXACTLY as defined below.

If user has not provided a feature request yet, ask: “Please describe the feature you want to develop.” Then WAIT.

After user provides feature request, execute steps in EXACT order: Step 1 → Step 2 → Step 3 → Step 4 → Step 5 → Step 6 → Step 7 → Step 8.

FORBIDDEN before Step 3 is complete:

• Do NOT write or modify any code
• Do NOT use Edit or Write tools
• Do NOT plan implementation details

Step 1: Analyze Requirement

Only summarize user’s requirement in plain text. Ask clarifying questions if needed. Do NOT explore codebase.

Step 2: Create GitHub Issue

gh issue create --title "[Feature] <description>" --body "<description and acceptance criteria>"

Tell user the Issue number and URL.

Step 3: Create Feature Branch

git fetch origin main
git checkout -b <issue-number>-<description> origin/main
git push -u origin <issue-number>-<description>

Tell user the branch name.

Step 4: Develop

Implement feature and write tests.

Step 5: Run Tests

# Go: go test ./... -v
# Python: pytest -v
# Node: npm test

If tests fail, fix and re-run.

Step 6: Commit and Push

git add <files>
git commit -m "feat: <description>

Closes #<issue-number>"
git push origin <branch-name>

Step 7: Deploy Staging (Gin/FastAPI only)

Check if project uses Gin or FastAPI. If not a Gin/FastAPI service, skip to Step 8.

7.1 Check for staging branch

git fetch origin
git branch -r | grep -q "origin/staging"

7.2a If staging branch exists: Merge to staging

git checkout staging
git pull origin staging
git merge <branch-name> --no-edit
git push origin staging
git checkout <branch-name>

Tell user: “Changes merged to staging branch. Staging deployment will be triggered automatically.”

7.2b If NO staging branch: Create beta tag

Get the latest tag and increment version:

# Get latest version tag (e.g., v1.2.3 or v1.2.3-beta.1)
git tag -l "v*" --sort=-v:refname | head -1

Create new beta tag with incremented version:

• If latest is vX.Y.Z, create vX.Y.Z-beta.1
• If latest is vX.Y.Z-beta.N, create vX.Y.Z-beta.(N+1)

git tag <new-beta-tag>
git push origin <new-beta-tag>

Tell user: “Created and pushed tag <new-beta-tag>. Staging deployment will be triggered automatically.”

Step 8: Create Pull Request

gh pr create --title "feat: <description>" --body "Closes #<issue-number>" --base main

Tell user the PR URL.

Workflow Summary

Non-service:  Requirement → Issue → Branch → Develop → Test → Push → PR
Gin/FastAPI:  Requirement → Issue → Branch → Develop → Test → Push → Staging → PR