claudes-office/template/claudes-office/tasks/README.md

CLI tool to initialize Claude's office in your project

# Tasks Directory

This directory contains detailed specifications for implementation tasks and tracks task progress.

## Purpose

The tasks directory helps:
1. Break down project work into manageable implementation tasks
2. Document detailed requirements for each task
3. Track task status and progress
4. Provide implementation guidance and acceptance criteria

## Usage

1. Create a task file for each significant implementation task
2. Include detailed specifications and acceptance criteria
3. Update task status as work progresses
4. Reference related plan documents and requirements

## Typical Contents

Each task file typically includes:
- Task identifier and name
- Detailed description and requirements
- Implementation approach
- Acceptance criteria
- Dependencies and prerequisites
- Status tracking
- References to related documents

## File Naming Convention

Use a consistent naming format that includes:
- Task identifier or category
- Brief description
- Status (optional)

Example:
```
auth_implement_login_flow.md
api_create_user_endpoint.md
ui_dashboard_components.md
```

## Organization

Tasks can be organized by component, feature, or status:

```
/tasks/
  /backlog/           # Tasks that are not yet started
  /in-progress/       # Tasks currently being worked on
  /completed/         # Completed tasks
  /feature1/          # Tasks related to Feature 1
  /feature2/          # Tasks related to Feature 2
```

or by priority:

```
/tasks/
  /critical/          # Critical priority tasks
  /high/              # High priority tasks
  /medium/            # Medium priority tasks
  /low/               # Low priority tasks
```

Feel free to adjust this structure based on your project's specific needs.