Implementation Workflow

Two Paths to Production

Choose your workflow based on task complexity:

Workflow	Time	Steps	Commands
My Kit	< 1 day	5	/mykit.*
Spec Kit	> 1 day	8	/speckit.* + /mykit.*

---

My Kit Workflow

Fast path for simple tasks.

Command Sequence

/mykit.backlog → /mykit.quickfix → /mykit.validate → /mykit.commit → /mykit.pr

Step-by-Step

1. Select Issue

/mykit.backlog

• View available issues
• Select one to work on
• Branch created automatically

2. Quick Fix

/mykit.quickfix

• Guided implementation
• Focuses on the specific fix
• Keeps scope contained

3. Validate

/mykit.validate --fix

• Runs lint, type check, build
• Auto-fixes common issues
• Ensures quality before commit

4. Commit

/mykit.commit

• Creates conventional commit
• Updates changelog
• Links to issue

5. Pull Request

/mykit.pr

• Creates PR with quality report
• Assigns reviewers
• Adds labels

6. Release (Optional)

/mykit.release

• Creates version tag
• Generates release notes
• Cleans up branch

My Kit Example

# Pick an issue
/mykit.backlog
# → Select: #45 "Fix mobile menu not closing"

# Implement the fix
/mykit.quickfix
# → Guided through the fix

# Validate
/mykit.validate --fix
# → All checks pass

# Commit
/mykit.commit
# → "fix: close mobile menu on navigation (#45)"

# Create PR
/mykit.pr
# → PR #46 created

---

Spec Kit Workflow

Comprehensive path for complex features.

Command Sequence

/speckit.init → /speckit.write → /speckit.review → Implementation → /mykit.validate → /mykit.commit → /mykit.pr → /mykit.release

Step-by-Step

1. Initialize Spec

/speckit.init

• Creates specs/{issue#}-{name}/ directory
• Generates spec template
• Creates feature branch

2. Write Spec

/speckit.write

• Fills in spec template
• Defines problem, goals, user stories
• Documents acceptance criteria

3. Review Spec

/speckit.review

• Validates spec completeness
• Checks for missing sections
• Ensures criteria are testable

4. Get Approval

/speckit.approve

• Marks spec as “Approved”
• Ready for implementation
• Stakeholders aligned

5. Implement

Build the feature according to spec:

• Follow deliverables list
• Check off items as completed
• Stay within scope

6. Validate

/mykit.validate --fix

• Run all quality checks
• Verify acceptance criteria
• Ensure spec compliance

7. Commit

/mykit.commit

• Conventional commit format
• Reference issue number
• Update changelog

8. Pull Request

/mykit.pr

• Comprehensive PR description
• Links to spec
• Quality metrics included

9. Release

/mykit.release

• Version bump
• Release notes from changelog
• Branch cleanup

Spec Kit Example

# Initialize spec for issue #50
/speckit.init
# → Created specs/50-user-dashboard/spec.md

# Write the specification
/speckit.write
# → Filled in problem, goals, user stories

# Review for completeness
/speckit.review
# → All sections complete

# Get approval
/speckit.approve
# → Status: Approved

# Implement (manual coding)
# ... build the feature ...

# Validate implementation
/mykit.validate --fix
# → All checks pass

# Commit changes
/mykit.commit
# → "feat: add user dashboard (#50)"

# Create PR
/mykit.pr
# → PR #51 created with quality report

# Release
/mykit.release
# → v1.5.0 released

---

Switching Workflows

When to Escalate

Started with My Kit but need more planning:

• Scope grew beyond original estimate
• Design decisions needed
• Multiple stakeholders involved
• Breaking changes required

How to Switch

1. Pause implementation
2. Run /speckit.init to create spec
3. Document current state and remaining work
4. Get spec reviewed
5. Continue implementation

Example Escalation

# Started as quick fix
/mykit.quickfix
# → Realized this needs more planning

# Escalate to Spec Kit
/speckit.init
# → Created spec document

# Document the feature properly
/speckit.write
# → Filled in full specification

# Continue with Spec Kit workflow
/speckit.review
/speckit.approve
# → Now properly specified

---

Workflow Comparison

Aspect	My Kit	Spec Kit
Planning	Minimal	Comprehensive
Documentation	Quick spec	Full spec
Review	Code only	Spec + code
Time	Hours	Days
Scope	Contained	Multi-file
Stakeholders	Just you	Team alignment

---

Command Reference

My Kit Commands

Command	Purpose
/mykit.backlog	Select issue
/mykit.quickfix	Guided fix
/mykit.validate	Quality checks
/mykit.commit	Create commit
/mykit.pr	Create PR
/mykit.release	Create release

Spec Kit Commands

Command	Purpose
/speckit.init	Initialize spec
/speckit.write	Generate template
/speckit.review	Validate spec
/speckit.approve	Mark approved

---

Best Practices

My Kit

• Keep changes focused
• Don’t expand scope mid-fix
• Validate before every commit
• One issue per PR

Spec Kit

• Write spec before coding
• Get approval before implementing
• Update spec if scope changes
• Track progress in checklist
• Don’t skip review