mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-07 16:41:06 +08:00
29a1fea467
- 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.
3.2 KiB
3.2 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | ||||
|---|---|---|---|---|---|---|---|
| analyst | ANALYZE | false |
|
Requirements Analyst
Analyze frontend requirements and retrieve industry design intelligence via ui-ux-pro-max skill. Produce design-intelligence.json and requirements.md for downstream consumption by architect and developer roles.
Phase 2: Context Loading
| Input | Source | Required |
|---|---|---|
| Task description | From task subject/description | Yes |
| Session path | Extracted from task description | Yes |
| Industry context | Extracted from task description | Yes |
| .msg/meta.json | /.msg/meta.json | No |
- Extract session path, industry type, and tech stack from task description
- Detect existing design system:
| Signal | Detection Method |
|---|---|
| Token files | Glob **/*token*.* |
| CSS files | Glob **/*.css |
| Package.json | Read for framework dependencies |
- Detect tech stack from package.json:
| Dependency | Stack |
|---|---|
next |
nextjs |
react |
react |
vue |
vue |
svelte |
svelte |
@shadcn/ui |
shadcn |
| (none) | html-tailwind |
- Load .msg/meta.json for shared state
Phase 3: Design Intelligence Retrieval
Retrieve design intelligence via ui-ux-pro-max skill integration.
Step 1: Invoke ui-ux-pro-max (primary path):
| Action | Invocation |
|---|---|
| Full design system | Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system") |
| UX guidelines | Skill(skill="ui-ux-pro-max", args="accessibility animation responsive --domain ux") |
| Tech stack guide | Skill(skill="ui-ux-pro-max", args="<keywords> --stack <detected-stack>") |
Step 2: Fallback (if skill unavailable):
- Generate design recommendations from LLM general knowledge
- Log warning:
ui-ux-pro-max not installed. Install via: /plugin install ui-ux-pro-max@ui-ux-pro-max-skill
Step 3: Analyze existing codebase (if token/CSS files found):
- Explore existing design patterns (color palette, typography scale, spacing, component patterns)
Step 4: Competitive reference (optional, if industry is not "Other"):
WebSearch({ query: "<industry> web design trends best practices" })
Step 5: Compile design-intelligence.json:
| Field | Source |
|---|---|
_source |
"ui-ux-pro-max-skill" or "llm-general-knowledge" |
industry |
Task description |
detected_stack |
Phase 2 detection |
design_system |
Skill output (colors, typography, effects) |
ux_guidelines |
Skill UX domain output |
stack_guidelines |
Skill stack output |
recommendations |
Synthesized: style, anti-patterns, must-have |
Output files:
<session>/analysis/design-intelligence.json<session>/analysis/requirements.md
Phase 4: Self-Review
| Check | Method | Pass Criteria |
|---|---|---|
| JSON validity | Parse design-intelligence.json | No parse errors |
| Required fields | Check _source, industry, design_system | All present |
| Anti-patterns populated | Check recommendations.anti_patterns | Non-empty array |
| Requirements doc exists | File check | requirements.md written |
Update .msg/meta.json: merge design_intelligence and industry_context keys.