mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-14 02:42:04 +08:00

Files

catlog22 cdb240d2c2 Add quality standards and team command design patterns documentation

- Introduced a new quality standards document outlining assessment criteria for team command .md files, including completeness, pattern compliance, integration, and consistency dimensions.
- Established quality gates and issue classification for errors, warnings, and informational notes.
- Created a comprehensive team command design patterns document detailing infrastructure and collaboration patterns, including message bus integration, YAML front matter requirements, task lifecycle, five-phase execution structure, and error handling.
- Included a pattern selection guide for collaboration scenarios to enhance team interaction models.

2026-02-13 23:39:06 +08:00

2.4 KiB

Raw Blame History

Phase 1: Session Discovery

Create or discover workflow session and initialize planning notes document.

Objective

Create a new workflow session via /workflow:session:start
Extract session ID for subsequent phases
Initialize planning-notes.md with user intent and N+1 context structure

Execution

Step 1.1: Execute Session Start

Skill(skill="workflow:session:start", args="--auto \"[structured-task-description]\"")

Task Description Structure:

GOAL: [Clear, concise objective]
SCOPE: [What's included/excluded]
CONTEXT: [Relevant background or constraints]

Example:

GOAL: Build JWT-based authentication system
SCOPE: User registration, login, token validation
CONTEXT: Existing user database schema, REST API endpoints

Step 1.2: Parse Output

Extract: SESSION_ID: WFS-[id] (store as sessionId)

Validation:

Session ID successfully extracted
Session directory .workflow/active/[sessionId]/ exists

Note: Session directory contains workflow-session.json (metadata). Do NOT look for manifest.json here - it only exists in .workflow/archives/ for archived sessions.

TodoWrite: Mark phase 1 completed, phase 2 in_progress

Step 1.3: Initialize Planning Notes

After Phase 1, initialize planning-notes.md with user intent:

// Create planning notes document with N+1 context support
const planningNotesPath = `.workflow/active/${sessionId}/planning-notes.md`
const userGoal = structuredDescription.goal
const userConstraints = structuredDescription.context || "None specified"

Write(planningNotesPath, `# Planning Notes

**Session**: ${sessionId}
**Created**: ${new Date().toISOString()}

## User Intent (Phase 1)

- **GOAL**: ${userGoal}
- **KEY_CONSTRAINTS**: ${userConstraints}

---

## Context Findings (Phase 2)
(To be filled by context-gather)

## Conflict Decisions (Phase 3)
(To be filled if conflicts detected)

## Consolidated Constraints (Phase 4 Input)
1. ${userConstraints}

---

## Task Generation (Phase 4)
(To be filled by action-planning-agent)

## N+1 Context
### Decisions
| Decision | Rationale | Revisit? |
|----------|-----------|----------|

### Deferred
- [ ] (For N+1)
`)

Output

Variable: sessionId (WFS-xxx)
File: .workflow/active/[sessionId]/planning-notes.md
TodoWrite: Mark Phase 1 completed, Phase 2 in_progress

Next Phase

Return to orchestrator, then auto-continue to Phase 2: Context Gathering.

2.4 KiB Raw Blame History