cc-development-workflow

# Development Workflow

**Purpose:** Establish efficient, high-quality development practices using AI code assistant agents and tools.

**Category:** Meta-Skill (Development Process)

---

## When to Use This Skill

This skill applies **throughout the entire development lifecycle**:

- Starting any new feature or bug fix
- Exploring unfamiliar code
- Making architectural decisions
- Committing changes
- Creating pull requests
- Reviewing code quality

**Triggers:**
- User requests a new feature
- User asks "where is..." or "how does..." questions
- You're about to implement without planning
- You're about to commit changes
- User asks for a PR

---

## Core Principle

**Use the right tool for the job.** Don't do manually what specialized agents can do better.

---

## Workflow 1: New Feature Development

### Triggers
- "Add...", "Build...", "Create...", "Implement [new thing]"
- User describes functionality that doesn't exist yet

### Decision Point: Should I use `/feature-dev`?

**Use `/feature-dev` if:**
- ✅ Feature requires multiple files
- ✅ Unclear how it should integrate with existing code
- ✅ Need to understand existing patterns first
- ✅ User hasn't specified exact implementation approach

**Skip `/feature-dev` if:**
- ❌ Trivial change (typo fix, single-line tweak)
- ❌ User provided extremely detailed implementation instructions
- ❌ Pure research/exploration task (use code-explorer instead)

### Workflow

**If using `/feature-dev`:**

```
1. Invoke Skill tool with skill="feature-dev:feature-dev"
2. Let the feature-dev workflow handle:
   - Codebase exploration
   - Clarifying questions
   - Architecture design
   - Implementation
   - Code review
3. Done - feature-dev handles end-to-end
```

**If NOT using `/feature-dev` (simple change):**

```
1. Read relevant files to understand current implementation
2. Ask clarifying questions if anything is ambiguous
3. Implement the change
4. Run build/lint/tests
5. Consider code-reviewer agent for non-trivial changes