Add document standards, quality gates, and templates for team lifecycle phases

- Introduced `document-standards.md` to define YAML frontmatter schema, naming conventions, and content structure for spec-generator outputs.
- Created `quality-gates.md` outlining per-phase quality gate criteria and scoring dimensions for spec-generator outputs.
- Added templates for architecture documents, epics and stories, product briefs, and requirements PRD to streamline documentation in respective phases.

.claude/skills/team-uidesign/SKILL.md

@@ -142,7 +142,7 @@ Cross-task knowledge accumulation. Coordinator creates `wisdom/` directory at se
 | Share state via team_msg(type='state_update') | Create tasks for other roles |
 | Delegate to commands/ files | Modify resources outside own responsibility |
 
-Coordinator additional restrictions: Do not write/modify code directly, do not call implementation subagents, do not execute analysis/audits, do not bypass workers.
+Coordinator additional restrictions: Do not write/modify code directly, do not spawn implementation workers directly, do not execute analysis/audits, do not bypass workers.
 
 ### Output Tagging
 

.claude/skills/team-uidesign/role-specs/researcher.md

@@ -1,7 +1,7 @@
 ---
 prefix: RESEARCH
 inner_loop: false
-subagents: [explore]
+additional_members: [explore]
 message_types:
   success: research_ready
   progress: research_progress
@@ -32,7 +32,7 @@ Analyze existing design system, build component inventory, assess accessibility
 | @shadcn/ui | shadcn |
 | (default) | html-tailwind |
 
-3. Use `explore` subagent to scan for existing design tokens, component files, styling patterns
+3. Use CLI tools (e.g., `ccw cli -p "..." --tool gemini --mode analysis`) or direct tools (Glob, Grep, mcp__ace-tool__search_context) to scan for existing design tokens, component files, styling patterns
 4. Read industry context from session config (industry, strictness, must-have features)
 
 ## Phase 3: Research Execution