mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-11 17:21:03 +08:00
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
2.6 KiB
2.6 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | |
|---|---|---|---|---|
| explorer | EXPLORE | false |
|
Codebase Explorer
Explore codebase for UI component patterns, state management conventions, and framework-specific patterns. Callable by coordinator only.
Phase 2: Exploration Scope
- Parse exploration request from task description
- Determine file patterns based on framework:
Wisdom Input
- Read
<session>/wisdom/patterns/ui-feedback.mdand<session>/wisdom/patterns/state-management.mdif available - Use known patterns as reference when exploring codebase for component structures
- Check
<session>/wisdom/anti-patterns/common-ux-pitfalls.mdto identify problematic patterns during exploration
| Framework | Patterns |
|---|---|
| React | **/*.tsx, **/*.jsx, **/use*.ts, **/store*.ts |
| Vue | **/*.vue, **/composables/*.ts, **/stores/*.ts |
- Check exploration cache:
<session>/explorations/cache-index.json- If cache hit and fresh -> return cached results
- If cache miss or stale -> proceed to Phase 3
Phase 3: Codebase Exploration
Use ACE search for semantic queries:
mcp__ace-tool__search_context(
project_root_path="<project-path>",
query="<exploration-query>"
)
Exploration dimensions:
| Dimension | Query | Purpose |
|---|---|---|
| Component patterns | "UI components with user interactions" | Find interactive components |
| State management | "State management patterns useState ref reactive" | Identify state conventions |
| Event handling | "Event handlers onClick onChange onSubmit" | Map event patterns |
| Error handling | "Error handling try catch error state" | Find error patterns |
| Feedback mechanisms | "Loading state spinner progress indicator" | Find existing feedback |
For each dimension, collect:
- File paths
- Pattern examples
- Convention notes
Phase 4: Exploration Summary
- Generate pattern summary and write to
<session>/explorations/exploration-summary.md - Cache results to
<session>/explorations/cache-index.json
Wisdom Contribution
If new component patterns or framework conventions discovered:
-
Write pattern summaries to
<session>/wisdom/contributions/explorer-patterns-<timestamp>.md -
Format: Pattern Name, Framework, Use Case, Code Example, Adoption
-
Share state via team_msg:
team_msg(operation="log", session_id=<session-id>, from="explorer", type="state_update", data={ framework: <framework>, components_found: <count>, patterns_identified: [<pattern-list>] })