claude-workflow

# Claude Workflow

Knowledge repository for Claude Workflow (CWF).

## Overview

CWF is a plan-driven development workflow using complementary documents that work together to guide feature implementation. All documents are stored in `.cwf/{feature-name}/`.

**Plan Document (`.cwf/{feature-name}/{feature-name}-plan.md`):**

- Captures architectural context and design rationale
- Documents WHY decisions were made and WHAT the solution is
- **Structure defined in `plan-spec.md`**

**Tasklist Document (`.cwf/{feature-name}/{feature-name}-tasklist.md`):**

- Provides step-by-step execution guidance
- Documents WHEN to do tasks and HOW to implement them
- **Structure defined in `tasklist-spec.md`**

**Mockup (`.cwf/{feature-name}/{feature-name}-mockup.html`) [Optional]:**

- Visual reference for UI/frontend features
- **Conventions defined in `mockup.md`**

**All documents follow the conformance requirements defined below.**

---

## Conventions

### Feature Naming

Feature names MUST:

- Use kebab-case (lowercase with hyphens)
- Be 1-3 words, concise and descriptive
- Contain only lowercase letters, numbers, and hyphens
- Start with a letter

Feature names MUST NOT contain uppercase, underscores, or start/end with hyphens.

**Validation pattern:** `^[a-z][a-z0-9]*(-[a-z0-9]+)*$`

**Examples:** `query-command`, `user-auth`, `oauth2-flow`

### Directory Structure

CWF planning documents MUST be stored in `.cwf/{feature-name}/`:

```text
.cwf/
└── {feature-name}/
    ├── {feature-name}-plan.md       [REQUIRED]
    ├── {feature-name}-tasklist.md   [REQUIRED]
    └── {feature-name}-mockup.html   [OPTIONAL]
```

The `.cwf/` directory is hidden to keep project root clean. Per-feature subdirectories contain related artifacts.

---

## Conformance and Tailoring

**All CWF planning documents (plans and tasklists) use RFC 2119 keywords to define requirements.**

The specifications in `plan-spec.md` and `tasklist-spec.md` use these keywords as described in RFC 2119.

- **MUST** / **