feat: standardize request_user_input schema across all codex skills and add config reminder

- Update all 68 .codex/skills files to use correct request_user_input schema
  (header, id, question, options with label/description)
- Remove deprecated multiSelect, type, value, prompt fields
- Add mandatory confirmation gates to planning-only skills
- Add Codex config.toml reminder to ccw install CLI
- Add Codex configuration section to README.md and README_CN.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
catlog22
2026-03-24 15:19:18 +08:00
parent ccb5f1e615
commit fe7945eaa2
72 changed files with 1020 additions and 901 deletions

View File

@@ -36,7 +36,7 @@ Evaluate quality metrics from the QUALITY-001 task, apply threshold checks, and
|------|------|---------|
| `Read` | builtin | Load quality results and task artifacts |
| `Bash` | builtin | Run verification commands (build check, test rerun) |
| `AskUserQuestion` | builtin | Present quality summary and obtain user verdict |
| `request_user_input` | builtin | Present quality summary and obtain user verdict |
---
@@ -108,7 +108,7 @@ Evaluate quality metrics from the QUALITY-001 task, apply threshold checks, and
- Per-metric breakdown with actual values vs thresholds
- List of unresolved findings (if any) with severity
- Recommendation (approve / reject with reasons)
2. Present to user via AskUserQuestion:
2. Present to user via request_user_input:
- If gate status is PASS: recommend approval
- If gate status is CONDITIONAL: present risks, ask user to decide
- If gate status is FAIL: recommend rejection with specific failures listed

View File

@@ -38,7 +38,7 @@ Parse user task input, detect pipeline signals, select execution mode, and produ
| `Glob` | builtin | Find existing artifacts in workspace |
| `Grep` | builtin | Search for keywords and patterns in artifacts |
| `Bash` | builtin | Run utility commands |
| `AskUserQuestion` | builtin | Clarify ambiguous requirements with user |
| `request_user_input` | builtin | Clarify ambiguous requirements with user |
---
@@ -90,7 +90,7 @@ Parse user task input, detect pipeline signals, select execution mode, and produ
| impl keywords + existing specs | `impl-only` |
| full-lifecycle keywords OR (impl keywords + no existing specs) | `full-lifecycle` |
| frontend keywords | `frontend` |
| Ambiguous / conflicting signals | Ask user via AskUserQuestion |
| Ambiguous / conflicting signals | Ask user via request_user_input |
2. If ambiguous, present options to user:
- Describe detected signals
@@ -155,7 +155,7 @@ Parse user task input, detect pipeline signals, select execution mode, and produ
| Scenario | Resolution |
|----------|------------|
| Requirement text is empty or too vague | Ask user for clarification via AskUserQuestion |
| Requirement text is empty or too vague | Ask user for clarification via request_user_input |
| Conflicting signals (e.g., "spec only" + "implement now") | Present conflict to user, ask for explicit choice |
| Existing artifacts are corrupted or incomplete | Log warning, treat as no-artifacts (full-lifecycle) |
| Workspace not writable | Report error, output JSON to stdout instead |