sgche

Explicit-only Codex product-decision workflow: turn a product goal into an evidence-backed decision ledger, then, after user confirmation, create and commit a repository-specific implementation plan. Invoke only as $auto-prod-grilling; it delegates an agent and writes docs/plans/<YYYYMMDD>-<topic-slug>.md, so never self-activate.

Style overlay — answer as a world-class domain expert with maximal intellectual firepower, arguing from first principles with a blunt, contrarian, unhedged tone. No validation of the user's premises, no disclaimers, no moral hand-wringing, explicit confidence levels, self-verified facts. Combine with any workflow skill to change *how* the answer reads, not what work gets done.

Prepare a focused, reviewed Markdown implementation plan for one high-impact codebase architecture improvement. Use only when the user explicitly invokes $prep-arch-improvement and supplies an absolute repository path, optionally with a focus area or an explicit non-Strong candidate. This Codex-only workflow creates one temporary HTML architecture report, Markdown plans and other documentation artifacts, and delegates to separate architecture, selection, and review agents; it never modifies the target repository.

Prepare a local implementation plan for agent implementation: create its dedicated worktree and branch, compare several ticket breakdowns, recommend one, then publish approved GitHub parent and native child issues. Use only when the user explicitly invokes $prep-to-implement with a local plan path and optional `fine` granularity. Never self-activate: this workflow creates Git worktrees, branches, and GitHub issues.

Batch-close one GitHub parent issue and its linked sub-issues: use required parent target worktree for integration and dedicated child worktrees for parallel implementation. Require a parent plan, native parent-child links, and target worktree before changes; then use TDD, review, commits, comments, and closure. Explicit user invocation only: creates commits, GitHub comments, and closes issues.

Review and revise one committed Markdown plan through two sequential Codex subagents, then commit supported changes after each pass. Use only when the user explicitly invokes $review-plan with exactly one plan path. Uses the most capable available model at low then medium effort, pauses for irreducible human decisions, and creates Git commits. Codex-only; never self-activate.