Enhance UX and Coordinator Role Constraints in Skills Documentation

- Added detailed constraints for the Coordinator role in the team UX improvement skill, emphasizing orchestration responsibilities and workflow management.
- Updated test cases in DashboardToolbar, useIssues, and useWebSocket to improve reliability and clarity.
- Introduced new tests for configStore and ignore patterns in Codex Lens to ensure proper functionality and configuration handling.
- Enhanced smart search functionality with improved embedding selection logic and added tests for various scenarios.
- Updated installation and usage documentation to reflect changes in directory structure and role specifications.
This commit is contained in:
catlog22
2026-03-08 23:43:44 +08:00
parent f3ae78f95e
commit 61ea9d47a6
110 changed files with 1516 additions and 218 deletions

View File

@@ -866,3 +866,41 @@ The orchestrator dynamically adds DEV-FE-NNN and QA-FE-NNN tasks to the state fi
| Requirements Template | templates/requirements-prd.md | DRAFT-002 |
| Architecture Template | templates/architecture-doc.md | DRAFT-003 |
| Epics Template | templates/epics-template.md | DRAFT-004 |
---
## Coordinator Role Constraints (Main Agent)
**CRITICAL**: The coordinator (main agent executing this skill) is responsible for **orchestration only**, NOT implementation.
15. **Coordinator Does NOT Execute Code**: The main agent MUST NOT write, modify, or implement any code directly. All implementation work is delegated to spawned team agents. The coordinator only:
- Spawns agents with task assignments
- Waits for agent callbacks
- Merges results and coordinates workflow
- Manages workflow transitions between phases
16. **Patient Waiting is Mandatory**: Agent execution takes significant time (typically 10-30 minutes per phase, sometimes longer). The coordinator MUST:
- Wait patiently for `wait()` calls to complete
- NOT skip workflow steps due to perceived delays
- NOT assume agents have failed just because they're taking time
- Trust the timeout mechanisms defined in the skill
17. **Use send_input for Clarification**: When agents need guidance or appear stuck, the coordinator MUST:
- Use `send_input()` to ask questions or provide clarification
- NOT skip the agent or move to next phase prematurely
- Give agents opportunity to respond before escalating
- Example: `send_input({ id: agent_id, message: "Please provide status update or clarify blockers" })`
18. **No Workflow Shortcuts**: The coordinator MUST NOT:
- Skip phases or stages defined in the workflow
- Bypass required approval or review steps
- Execute dependent tasks before prerequisites complete
- Assume task completion without explicit agent callback
- Make up or fabricate agent results
19. **Respect Long-Running Processes**: This is a complex multi-agent workflow that requires patience:
- Total execution time may range from 30-90 minutes or longer
- Each phase may take 10-30 minutes depending on complexity
- The coordinator must remain active and attentive throughout the entire process
- Do not terminate or skip steps due to time concerns

View File

@@ -5,7 +5,7 @@ Seed analysis, codebase exploration (via shared explore subagent), and multi-dim
## Identity
- **Type**: `produce`
- **Role File**: `~/.codex/skills/team-lifecycle/agents/analyst.md`
- **Role File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/analyst.md`
- **Prefix**: `RESEARCH-*`
- **Tag**: `[analyst]`
- **Responsibility**: Seed Analysis -> Codebase Exploration -> Context Packaging -> Inline Discuss -> Report
@@ -168,7 +168,7 @@ if (cached) {
// Cache MISS - spawn explore subagent
const explorer = spawn_agent({
message: `### MANDATORY FIRST STEPS
1. Read: ~/.codex/skills/team-lifecycle/agents/explore-agent.md
1. Read: ~/~ or <project>/.codex/skills/team-lifecycle/agents/explore-agent.md
---
@@ -253,7 +253,7 @@ After packaging, spawn discuss subagent (Pattern 2.8):
```javascript
const critic = spawn_agent({
message: `### MANDATORY FIRST STEPS
1. Read: ~/.codex/skills/team-lifecycle/agents/discuss-agent.md
1. Read: ~/~ or <project>/.codex/skills/team-lifecycle/agents/discuss-agent.md
## Multi-Perspective Critique: DISCUSS-001
@@ -297,7 +297,7 @@ This agent spawns two utility subagents during its execution:
### Explore Subagent (Phase 3)
**When**: After seed analysis, when project files detected
**Agent File**: `~/.codex/skills/team-lifecycle/agents/explore-agent.md`
**Agent File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/explore-agent.md`
**Pattern**: 2.9 (Cache-Aware Exploration)
See Phase 3 code block above. Cache is checked before spawning. If cache hit, the spawn is skipped entirely.
@@ -305,7 +305,7 @@ See Phase 3 code block above. Cache is checked before spawning. If cache hit, th
### Discuss Subagent (Phase 4b)
**When**: After context packaging (spec-config.json + discovery-context.json written)
**Agent File**: `~/.codex/skills/team-lifecycle/agents/discuss-agent.md`
**Agent File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/discuss-agent.md`
**Pattern**: 2.8 (Inline Subagent)
See Phase 4b code block above.
@@ -342,7 +342,7 @@ if (cached) {
// Cache MISS - spawn explore subagent, result cached by explore-agent
const explorer = spawn_agent({
message: `### MANDATORY FIRST STEPS
1. Read: ~/.codex/skills/team-lifecycle/agents/explore-agent.md
1. Read: ~/~ or <project>/.codex/skills/team-lifecycle/agents/explore-agent.md
---

View File

@@ -5,7 +5,7 @@ Lightweight multi-perspective critique engine. Called inline by produce agents (
## Identity
- **Type**: `utility`
- **Role File**: `~/.codex/skills/team-lifecycle/agents/discuss-agent.md`
- **Role File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/discuss-agent.md`
- **Tag**: `[discuss]`
- **Responsibility**: Read Artifact -> Multi-CLI Perspective Analysis -> Divergence Detection -> Consensus Determination -> Write Discussion Record -> Return Verdict

View File

@@ -5,7 +5,7 @@ Shared codebase exploration utility with centralized caching. Callable by any ag
## Identity
- **Type**: `utility`
- **Role File**: `~/.codex/skills/team-lifecycle/agents/explore-agent.md`
- **Role File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/explore-agent.md`
- **Tag**: `[explore]`
- **Responsibility**: Cache Check -> Codebase Exploration -> Cache Update -> Return Structured Results
@@ -382,7 +382,7 @@ if (cached && !forceRefresh) {
// After seed analysis, explore codebase context (Pattern 2.9 in analyst)
const explorer = spawn_agent({
message: `### MANDATORY FIRST STEPS
1. Read: ~/.codex/skills/team-lifecycle/agents/explore-agent.md
1. Read: ~/~ or <project>/.codex/skills/team-lifecycle/agents/explore-agent.md
---
@@ -405,7 +405,7 @@ for (const angle of angles) {
// Cache check happens inside explore-agent
const explorer = spawn_agent({
message: `### MANDATORY FIRST STEPS
1. Read: ~/.codex/skills/team-lifecycle/agents/explore-agent.md
1. Read: ~/~ or <project>/.codex/skills/team-lifecycle/agents/explore-agent.md
---

View File

@@ -5,7 +5,7 @@ Product Brief, Requirements/PRD, Architecture, and Epics & Stories document gene
## Identity
- **Type**: `produce`
- **Role File**: `~/.codex/skills/team-lifecycle/agents/writer.md`
- **Role File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/writer.md`
- **Prefix**: `DRAFT-*`
- **Tag**: `[writer]`
- **Responsibility**: Load Context -> Generate Document -> Self-Validation -> Inline Discuss -> Report
@@ -382,7 +382,7 @@ After validation, spawn discuss subagent (Pattern 2.8) for this task's discuss r
```javascript
const critic = spawn_agent({
message: `### MANDATORY FIRST STEPS
1. Read: ~/.codex/skills/team-lifecycle/agents/discuss-agent.md
1. Read: ~/~ or <project>/.codex/skills/team-lifecycle/agents/discuss-agent.md
## Multi-Perspective Critique: <DISCUSS-NNN>
@@ -435,7 +435,7 @@ This agent spawns the discuss subagent during Phase 4b:
### Discuss Subagent (Phase 4b)
**When**: After self-validation of generated document
**Agent File**: `~/.codex/skills/team-lifecycle/agents/discuss-agent.md`
**Agent File**: `~/~ or <project>/.codex/skills/team-lifecycle/agents/discuss-agent.md`
**Pattern**: 2.8 (Inline Subagent)
See Phase 4b code block above. The round ID and perspectives vary per doc type -- use the Inline Discuss Mapping table.

View File

@@ -1,6 +1,6 @@
# Phase 1: Requirement Clarification
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/.codex/skills/team-lifecycle/phases/01-requirement-clarification.md")` before continuing. Never execute based on summaries.
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/~ or <project>/.codex/skills/team-lifecycle/phases/01-requirement-clarification.md")` before continuing. Never execute based on summaries.
## Objective

View File

@@ -1,6 +1,6 @@
# Phase 2: Team Initialization
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/.codex/skills/team-lifecycle/phases/02-team-initialization.md")` before continuing. Never execute based on summaries.
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/~ or <project>/.codex/skills/team-lifecycle/phases/02-team-initialization.md")` before continuing. Never execute based on summaries.
## Objective

View File

@@ -1,6 +1,6 @@
# Phase 3: Task Chain Creation
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/.codex/skills/team-lifecycle/phases/03-task-chain-creation.md")` before continuing. Never execute based on summaries.
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/~ or <project>/.codex/skills/team-lifecycle/phases/03-task-chain-creation.md")` before continuing. Never execute based on summaries.
## Objective

View File

@@ -1,6 +1,6 @@
# Phase 4: Pipeline Coordination
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/.codex/skills/team-lifecycle/phases/04-pipeline-coordination.md")` before continuing. Never execute based on summaries.
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/~ or <project>/.codex/skills/team-lifecycle/phases/04-pipeline-coordination.md")` before continuing. Never execute based on summaries.
## Objective

View File

@@ -1,6 +1,6 @@
# Phase 5: Completion Report
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/.codex/skills/team-lifecycle/phases/05-completion-report.md")` before continuing. Never execute based on summaries.
> **COMPACT PROTECTION**: This is an execution document. After context compression, phase instructions become summaries only. You MUST immediately re-read this file via `Read("~/~ or <project>/.codex/skills/team-lifecycle/phases/05-completion-report.md")` before continuing. Never execute based on summaries.
## Objective