zen-workflow

# zen Workflow Skill

This skill provides context for zen workflow operations.

## Auto-Activation Keywords

- Issue, PR, Pull Request
- workflow, zen
- branch, commit
- GitHub Projects
- review, lint

## Context

When activated, this skill provides:

1. **Workflow Awareness**
   - Current branch and associated Issue
   - Work memory state
   - Status in GitHub Projects

2. **Command Guidance**
   - Suggest appropriate commands
   - Remind about work memory updates
   - Guide through workflow steps

3. **Best Practices**
   - Conventional Commits format
   - Branch naming conventions
   - PR template usage

4. **Coding Principles**
   - AI コーディングの失敗パターン回避
   - 詳細は [references/coding-principles.md](./references/coding-principles.md) を参照

5. **Common Principles**
   - AskUserQuestion の過剰使用削減
   - 詳細は [references/common-principles.md](./references/common-principles.md) を参照

## Workflow State Detection

Detect current state from:
- Branch name pattern: `{type}/issue-{number}-*`
  - `{type}` の値: `feat`, `fix`, `docs`, `refactor`, `chore`, `style`, `test`
  - `style` はコードスタイル・フォーマット変更（ロジック変更なし）に使用
- Git status
- Open PRs

## Suggested Actions

| State | Suggestion |
|-------|------------|
| On main/develop, no Issue | `/zen:issue:create` or `/zen:issue:list` |
| On feature branch, no PR | `/zen:pr:create` after work |
| PR open, draft | `/zen:pr:review` then `/zen:pr:ready` |
| Long session (30分以上経過) | `/zen:issue:update` |

## Confirmation Aggregation Rules

During work sessions, confirmation requests should be aggregated rather than asked immediately. This enables more efficient workflows.

**Note**: Before aggregating a confirmation request, use the `question_self_check` principle (see [references/common-principles.md](./references/common-principles.md)) to verify the question is truly necessary. Only questions that pass the self-check should be aggregated.

### Aggregation Rules

1. **Accumulate Confirmations**
   - Do not interrupt work to ask questions for every min