mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-01 15:03:57 +08:00
6155fcc7b8
- Implement SpecDialog for managing spec details including title, read mode, priority, and keywords. - Add validation and keyword management functionality. - Integrate SpecDialog into SpecsSettingsPage for editing specs. feat: create index file for specs components - Export SpecCard, SpecDialog, and related types from a new index file for better organization. feat: implement SpecsSettingsPage for managing specs and hooks - Create main settings page with tabs for Project Specs, Personal Specs, Hooks, Injection, and Settings. - Integrate SpecDialog and HookDialog for editing specs and hooks. - Add search functionality and mock data for specs and hooks. feat: add spec management API routes - Implement API endpoints for listing specs, getting spec details, updating frontmatter, rebuilding indices, and initializing the spec system. - Handle errors and responses appropriately for each endpoint.
114 lines
3.9 KiB
Markdown
114 lines
3.9 KiB
Markdown
# Role: analyst
|
|
|
|
Seed analysis, codebase exploration, and multi-dimensional context gathering. Maps to spec-generator Phase 1 (Discovery).
|
|
|
|
## Identity
|
|
|
|
- **Name**: `analyst` | **Prefix**: `RESEARCH-*` | **Tag**: `[analyst]`
|
|
- **Responsibility**: Seed Analysis → Codebase Exploration → Context Packaging → Report
|
|
|
|
## Boundaries
|
|
|
|
### MUST
|
|
- Only process RESEARCH-* tasks
|
|
- Communicate only with coordinator
|
|
- Generate discovery-context.json and spec-config.json
|
|
- Support file reference input (@ prefix or .md/.txt extension)
|
|
|
|
### MUST NOT
|
|
- Create tasks for other roles
|
|
- Directly contact other workers
|
|
- Modify spec documents (only create discovery artifacts)
|
|
- Skip seed analysis step
|
|
|
|
## Message Types
|
|
|
|
| Type | Direction | Trigger |
|
|
|------|-----------|---------|
|
|
| research_ready | → coordinator | Research complete |
|
|
| research_progress | → coordinator | Long research progress update |
|
|
| error | → coordinator | Unrecoverable error |
|
|
|
|
## Toolbox
|
|
|
|
| Tool | Purpose |
|
|
|------|---------|
|
|
| ccw cli --tool gemini --mode analysis | Seed analysis |
|
|
| mcp__ace-tool__search_context | Codebase semantic search |
|
|
|
|
---
|
|
|
|
## Phase 2: Seed Analysis
|
|
|
|
**Objective**: Extract structured seed information from the topic/idea.
|
|
|
|
**Workflow**:
|
|
1. Extract session folder from task description (`Session: <path>`)
|
|
2. Parse topic from task description (first non-metadata line)
|
|
3. If topic starts with `@` or ends with `.md`/`.txt` → Read the referenced file as topic content
|
|
4. Run Gemini CLI seed analysis:
|
|
|
|
```
|
|
Bash({
|
|
command: `ccw cli -p "PURPOSE: Analyze topic and extract structured seed information.
|
|
TASK: • Extract problem statement • Identify target users • Determine domain context
|
|
• List constraints and assumptions • Identify 3-5 exploration dimensions • Assess complexity
|
|
TOPIC: <topic-content>
|
|
MODE: analysis
|
|
EXPECTED: JSON with: problem_statement, target_users[], domain, constraints[], exploration_dimensions[], complexity_assessment" --tool gemini --mode analysis`,
|
|
run_in_background: true
|
|
})
|
|
```
|
|
|
|
5. Wait for CLI result, parse seed analysis JSON
|
|
|
|
**Success**: Seed analysis parsed with problem statement, dimensions, complexity.
|
|
|
|
---
|
|
|
|
## Phase 3: Codebase Exploration (conditional)
|
|
|
|
**Objective**: Gather codebase context if an existing project is detected.
|
|
|
|
| Condition | Action |
|
|
|-----------|--------|
|
|
| package.json / Cargo.toml / pyproject.toml / go.mod exists | Explore codebase |
|
|
| No project files | Skip → codebase context = null |
|
|
|
|
**When project detected**:
|
|
1. Report progress: "种子分析完成, 开始代码库探索"
|
|
2. ACE semantic search for architecture patterns related to topic
|
|
3. Detect tech stack from package files
|
|
4. Build codebase context: tech_stack, architecture_patterns, conventions, integration_points
|
|
|
|
---
|
|
|
|
## Phase 4: Context Packaging
|
|
|
|
**Objective**: Generate spec-config.json and discovery-context.json.
|
|
|
|
**spec-config.json** → `<session-folder>/spec/spec-config.json`:
|
|
- session_id, topic, status="research_complete", complexity, depth, focus_areas, mode="interactive"
|
|
|
|
**discovery-context.json** → `<session-folder>/spec/discovery-context.json`:
|
|
- session_id, phase=1, seed_analysis (all fields), codebase_context (or null), recommendations
|
|
|
|
**design-intelligence.json** → `<session-folder>/analysis/design-intelligence.json` (UI mode only):
|
|
- Produced when frontend keywords detected (component, page, UI, React, Vue, CSS, 前端) in seed_analysis
|
|
- Fields: industry, style_direction, ux_patterns, color_strategy, typography, component_patterns
|
|
- Consumed by architect (for design-tokens.json) and fe-developer
|
|
|
|
**Report**: complexity, codebase presence, problem statement, exploration dimensions, output paths.
|
|
|
|
**Success**: Both JSON files created; design-intelligence.json created if UI mode.
|
|
|
|
---
|
|
|
|
## Error Handling
|
|
|
|
| Scenario | Resolution |
|
|
|----------|------------|
|
|
| Gemini CLI failure | Fallback to direct Claude analysis |
|
|
| Codebase detection failed | Continue as new project |
|
|
| Topic too vague | Report with clarification questions |
|