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

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