feat: add SpecDialog component for editing spec frontmatter

- 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.

.claude/skills/team-lifecycle-v3/roles/analyst/role.md

@@ -93,9 +93,14 @@ EXPECTED: JSON with: problem_statement, target_users[], domain, constraints[], e
 **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, report sent.
+**Success**: Both JSON files created; design-intelligence.json created if UI mode.
 
 ---
 

.claude/skills/team-lifecycle-v3/roles/architect/role.md

@@ -78,7 +78,11 @@ For complex questions → Gemini CLI with architecture review rule.
 
 Output to `<session-folder>/architecture/arch-<slug>.json`. Contribute decisions to wisdom/decisions.md.
 
-**Report**: mode, verdict, concern count, recommendations, output path.
+**Frontend project outputs** (when frontend tech stack detected in shared-memory or discovery-context):
+- `<session-folder>/architecture/design-tokens.json` — color, spacing, typography, shadow tokens
+- `<session-folder>/architecture/component-specs/*.md` — per-component design spec
+
+**Report**: mode, verdict, concern count, recommendations, output path(s).
 
 ---
 

.claude/skills/team-lifecycle-v3/roles/discussant/role.md

@@ -105,6 +105,17 @@ Delegate to `commands/critique.md` -- launches parallel CLI calls per perspectiv
 
 Write discussion record to `<session-folder>/discussions/<output-file>`.
 
+**Output file naming convention**:
+
+| Round | Output File |
+|-------|------------|
+| DISCUSS-001 | discuss-001-scope.md |
+| DISCUSS-002 | discuss-002-brief.md |
+| DISCUSS-003 | discuss-003-requirements.md |
+| DISCUSS-004 | discuss-004-architecture.md |
+| DISCUSS-005 | discuss-005-epics.md |
+| DISCUSS-006 | discuss-006-signoff.md |
+
 ---
 
 ## Error Handling

.claude/skills/team-lifecycle-v3/roles/reviewer/commands/spec-quality.md

@@ -15,14 +15,14 @@
 
 **Spec document phases** (matched by filename/directory):
 
-| Phase | Expected Path |
-|-------|--------------|
-| product-brief | spec/product-brief.md |
-| prd | spec/requirements/*.md |
-| architecture | spec/architecture/_index.md + ADR-*.md |
-| user-stories | spec/epics/*.md |
-| implementation-plan | plan/plan.json |
-| test-strategy | spec/test-strategy.md |
+| Phase | Expected Path | Required |
+|-------|--------------|---------|
+| product-brief | spec/product-brief.md | Yes |
+| prd | spec/requirements/*.md | Yes |
+| architecture | spec/architecture/_index.md + ADR-*.md | Yes |
+| user-stories | spec/epics/*.md | Yes |
+| implementation-plan | plan/plan.json | No (impl-only/full-lifecycle) |
+| test-strategy | spec/test-strategy.md | No (optional, not generated by pipeline) |
 
 ## Phase 3: 5-Dimension Scoring
 
@@ -51,7 +51,8 @@ Check each spec document for required sections.
 | architecture | System Overview, Component Design, Data Models, API Specifications, Technology Stack |
 | user-stories | Story List, Acceptance Criteria, Priority, Estimation |
 | implementation-plan | Task Breakdown, Dependencies, Timeline, Resource Allocation |
-| test-strategy | Test Scope, Test Cases, Coverage Goals, Test Environment |
+
+> **Note**: `test-strategy` is optional — skip scoring if `spec/test-strategy.md` is absent. Do not penalize completeness score for missing optional phases.
 
 **Scoring formula**:
 - Section present: 50% credit