Skill: /dev-workflow

Usage

/dev-workflow {task_type} {description}

Examples:

/dev-workflow feature "add product filtering by category"
/dev-workflow update "refactor user authentication to use Sanctum tokens"
/dev-workflow fix "cart total not updating on quantity change"

15-Step Process

Execute each step in strict order. Present the current step number and name as a header before each action so the lead can track progress.

► STEP 1 — Create Branch

Invoke /git-start with the correct type and domain derived from the task.

/git-start {type} {domain} {normalized-description}

• type: feature | fix | refactor | chore
• domain: infer from task description (auth / products / cart / orders / notifications / infra / shared / etc.)
• Confirm branch name to lead before proceeding

Checkpoint: Lead confirms branch name → proceed to Step 2

► STEP 2 — Read Reference Files

Invoke /read-references to load all relevant context maps.

/read-references {technology}

• technology: laravel | react | react-native | frontend | all
• This step is MANDATORY — do NOT skip to plan without reading references

Checkpoint: References loaded and summarized → proceed to Step 3

► STEP 3 — Prepare Plan (Plan Mode)

Invoke /plan-feature to enter read-only analysis and produce a structured implementation plan.

/plan-feature "{task_description}"

• Analyze reference files for relevant files to touch
• List every file to create or modify
• Describe the change in each file in 1–2 sentences
• Estimate risk level: low / medium / high
• Flag any breaking changes

Checkpoint: Lead reviews and approves the plan → proceed to Step 4 If rejected: revise plan and re-present. Do NOT implement until approved.

► STEP 4 — Implement the Plan

Invoke /implement-plan to execute the approved plan.

/implement-plan

• Implement ONLY what was approved in the plan
• Do not add undiscussed changes ("while I was in there...")
• After each logical unit (e.g., migration + model, or component + hook), summarize what was done
• Surface any discovered complications immediately

Checkpoint: All files in the plan implemented → proceed to Step 5

► STEP 5 — Commit the Changes

Invoke /git-commit to stage and commit the implementation.

/git-commit

• Follow Conventional Commits format
• Commit scope = domain from branch name
• Body explains WHY, not what the diff shows

Checkpoint: Commit created and confirmed → proceed to Step 6

► STEP 6 — Create PR and Summary

Invoke /create-pr to push the branch and open a pull request.

/create-pr "{task_description}"

• Push branch to remote
• Generate PR title and description
• Include: what changed, why, testing done, screenshots (if UI)
• Link to any related issues or tickets

Checkpoint: PR created with URL confirmed → proceed to Step 7

► STEP 7 — Test and Error Check (Lint / Test)

Invoke /test-lint for the appropriate technology.

/test-lint {technology}

• Run linter (PHP CS Fixer / ESLint / Stylelint)
• Run test suite (Pest / Vitest / Jest)
• Run type checker if applicable (TypeScript)
• Collect ALL errors before reporting — do not fix one at a time

Checkpoint (PASS): Zero errors → proceed to Step 12 Checkpoint (FAIL): Errors found → proceed to Step 8

► STEP 8 — Prepare Fix Plan (if errors from Step 7)

Invoke /fix-plan to analyze errors and prepare a targeted fix.

/fix-plan

• Categorize errors by type and root cause
• Propose minimal targeted fixes (no scope creep)
• Present fix plan to lead for approval

Checkpoint: Lead approves fix plan → proceed to Step 9

► STEP 9 — Implement the Fix Plan

Invoke /implement-fix to apply the approved fixes.

/implement-fix

• Apply ONLY the approved fixes
• Do not introduce new logic while fixing

Checkpoint: All fixes applied → proceed to Step 10

► STEP 10 — Commit the Final Changes

Invoke /git-commit again for the fix changes.

/git-commit

• Commit type: fix
• Body explains what test/lint error was corrected

Checkpoint: Fix committed → proceed to Step 11

► STEP 11 — Run Tests Again

Invoke /test-lint a second time to confirm all errors are resolved.

/test-lint {technology}

Checkpoint (PASS): Zero errors → proceed to Step 12 Checkpoint (FAIL): Return to Step 8. If 3 fix cycles fail, escalate to lead.

► STEP 12 — Merge into Master / Main

Invoke /merge-main to merge the PR.

/merge-main

• Confirm all PR checks are green
• Squash merge with a clean commit message
• Delete remote branch after merge

Checkpoint: Merged and confirmed → proceed to Step 13

► STEP 13 — Update the Reference Files

Invoke /update-references to keep the project map accurate.

/update-references auto

• This step is MANDATORY — skipping it breaks future AI context
• Update every reference file affected by the changes in this task

Note: Task completion should be blocked until the affected reference maps have been refreshed.

Checkpoint: Reference files updated and confirmed → proceed to Step 14

► STEP 14 — Delete the Branch

Invoke /delete-branch to clean up.

/delete-branch

• Delete local branch
• Confirm remote was already deleted in Step 12

Checkpoint: Branch deleted → proceed to Step 15

► STEP 15 — Complete

Report final status to lead:

✅ WORKFLOW COMPLETE

Task    : {task_type} — {description}
Branch  : {branch_name} (deleted)
PR      : {pr_url} (merged)
Commits : {commit_hashes}
Refs    : {list of updated reference files}
Duration: {start → end}

Error Escalation Policy

If the workflow cannot proceed due to a blocking issue at any step:

1. Stop immediately and report the blocker clearly
2. Do NOT attempt workarounds without lead approval
3. State which step is blocked and what information is needed
4. Resume from the blocked step once resolved — do NOT restart from Step 1