Convert 20 agent .md files to Codex-native .toml format with proper
metadata (name, description, model, sandbox_mode, developer_instructions).
Update all 19 skill files to use agent_type references instead of .md
file paths. Remove "Read role definition" bootstrapping step from spawn
messages since TOML developer_instructions replaces it.
Agent format: YAML frontmatter + body → TOML with inline instructions
Calling schema: agent: "path.md" → agent_type: "toml_name"
Sandbox: read-only for exploration agents, workspace-write for executors
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Rename skill directory from workflow-lite-plan to workflow-lite-planex (planex = plan + execute)
- Remove standalone lite-execute command entry from command.json and analyze_commands.py
- Update all 60+ files referencing workflow-lite-plan to use workflow-lite-planex
- Update descriptions to clarify Phase 1: plan → Phase 2: execute architecture
- Remove lite-execute as standalone command from orchestrator routing tables
- Update docs (EN/ZH) to reflect unified planex naming and phase descriptions
Add explicit constraints preventing Phase 3 interactive rounds from
modifying source code. Feedback handlers now clearly scope updates to
roadmap.md and issues.jsonl only, with code changes deferred to handoff.
docs: add team lifecycle orchestrator skill documentation with detailed architecture, agent registry, and execution phases
docs: introduce team planex skill for issue-by-issue execution with Codex CLI, including input parsing and session management
- Replace non-existent `--tag` and `--session` options with actual commands
- Update to use `ccw issue list --status` and queue-based workflow
- Sync changes across both Claude and Codex versions
- Created a new directory structure for epics and stories with templates for individual epics and an index file.
- Added a product brief template for generating product brief documents in Phase 2.
- Introduced a requirements PRD template for generating a Product Requirements Document as a directory of individual requirement files in Phase 3.
feat: implement V2PipelineTab component for Memory V2 management
- Developed the V2PipelineTab component to manage extraction and consolidation processes.
- Included ExtractionCard and ConsolidationCard components to handle respective functionalities.
- Added JobsList component to display job statuses and allow filtering by job kind.
feat: create hooks for Memory V2 pipeline
- Implemented custom hooks for managing extraction and consolidation statuses, as well as job listings.
- Added mutation hooks to trigger extraction and consolidation processes with automatic query invalidation on success.
