Conflux Proposal Creator

Create structured change proposals for Conflux (OpenSpec-based) projects through interactive conversation with users.

Scope Restrictions (Proposal-Only)

• This skill is for proposal creation only. Do NOT implement or modify product/source code.
• You may READ any files for context gathering.
• You may WRITE only under openspec/changes/<change-id>/.
• After strict validation passes, stop and present the proposal for review.

Guardrails (Match Command Behavior)

• Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
• Keep changes tightly scoped to the requested outcome.
• Default to proposal splitting: when requirements can be decomposed into independent scopes, create separate change proposals.
• If uncertain whether to split, prefer splitting unless the scopes are tightly coupled and must ship together to preserve correctness.
• For each split proposal, use a distinct verb-led change-id and keep proposal.md, tasks.md, and design.md (when needed) scoped to that proposal only.
• When multiple proposals are created, explicitly document dependency/sequence relationships and parallelizability in the final user-facing summary.