jed-zed/ccg-codex-workflow/ccg-feat

CCG Feature

Load and follow skills/ccg-executor/SKILL.md.

Use this as the Codex-native equivalent of the original CCG /ccg:feat command.

Behavior

• Treat the user argument as a feature request.
• If the request is broad or ambiguous, create a short in-chat implementation outline before editing. For high-impact ambiguity, ask a concise Chinese question.
• Gather context first; prefer ace-tool when available, then rg and targeted reads.
• Codex owns all file edits, verification, diff review, and Chinese delivery.
• Gemini is optional for simple backend-heavy features, but useful for complex design alternatives, edge cases, prototype patches, UI implications, or second-pass review.
• Whenever Gemini is used, invoke ../ccg-executor/scripts/invoke_gemini_preview.py directly with the bundled browser preview helper. Do not ask the user to run /ccg:gemini-preview manually and do not call the raw Gemini CLI.
• Prefer --prompt-template prototype for implementation sketches and --prompt-template review for second-pass review.

Verification

• Run the narrowest relevant project tests or type checks.
• For changes over roughly 30 lines, also run or equivalently perform /ccg:verify-change and /ccg:verify-quality <changed-path>.
• For auth, permissions, validation, secrets, file uploads, command execution, or network boundaries, run or equivalently perform /ccg:verify-security <changed-path>.