feature-initlisted

# Feature Init (Codex) Match the user's language. Read [`../../../../docs/actions/feature-init.md`](../../../../docs/actions/feature-init.md) completely before acting; it owns classification, workflow, outputs, and safety rules. - Resolve the target root explicitly and read applicable `AGENTS.md` plus active current truth; never write under an incidental cwd. - Resolve the plugin root as the nearest ancestor of this skill containing `.codex-plugin/plugin.json`; invoke its `scripts/materialize-feature-artifact.cjs` and never bypass the no-clobber gate. - Apply the action's impact/necessity preflight, scope-viability, deferred-outcome, and progressive-read boundaries exactly. Resolve high-impact business, ownership, authorization, data-disposition, and release-coupling questions before materialization; normal small/medium single-outcome and no-artifact paths need no extra gate narration. - Classify `PREVIEW` versus `APPLY` from the user's requested operation. `PREVIEW` never invokes the materializer, dispatches the auditor, or writes files; invocation alone is not write authorization. Reuse a compatible active feature instead of allocating a duplicate number. - When the selected change establishes or materially changes project-wide application architecture, read [`../../../../docs/architecture-design.md`](../../../../docs/architecture-design.md) completely and use only its applicable conversational-fill topics; ordinary features skip it. - When a tier/module boundary ch