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-planex/SKILL.md

@@ -127,7 +127,7 @@ When coordinator spawns workers, use `team-worker` agent with role-spec path:
 
 ```
 Agent({
-  subagent_type: "team-worker",
+  agent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: <team-name>,
   name: "<role>",

.claude/skills/team-planex/role-specs/executor.md

@@ -85,6 +85,6 @@ Send `impl_complete` message to coordinator via team_msg + SendMessage.
 |---------|-----------|
 | Load solution from file | Create or modify issues |
 | Implement via CLI tools (Codex/Gemini) | Modify solution artifacts |
-| Run tests | Spawn subagents (use CLI tools instead) |
+| Run tests | Spawn additional agents (use CLI tools instead) |
 | git commit | Direct user interaction |
 | Update issue status | Create tasks for other roles |

.claude/skills/team-planex/roles/coordinator/commands/monitor.md

@@ -118,7 +118,7 @@ Collect task states from TaskList()
       |   +- EXEC-* -> executor
       +- Spawn team-worker:
          Agent({
-           subagent_type: "team-worker",
+           agent_type: "team-worker",
            description: "Spawn <role> worker for <subject>",
            team_name: <team-name>,
            name: "<role>",

.claude/skills/team-planex/roles/coordinator/role.md

@@ -19,7 +19,7 @@ Orchestrate the team-planex pipeline: parse input, create team, dispatch tasks,
 ### MUST NOT
 - Execute planning or implementation work directly (delegate to workers)
 - Modify solution artifacts or code (workers own their deliverables)
-- Call implementation subagents (code-developer, etc.) directly
+- Call implementation CLI tools (code-developer, etc.) directly
 - Skip dependency validation when creating task chains
 
 ---