Propose Feature

Produce one proposal that a reader with no access to the conversation can understand and assess. Use the common Feature proposal form for requests, improvements and proposed commands. This skill ends with a reviewable draft or an authorized, filed issue.

Read the contribution workflow for when a proposal is needed and what follows acceptance. Use contribute when selecting the contribution route or preparing implementation. Follow that policy; a user may also request a proposal draft for work whose route does not require one.

The repository is public. Follow the anonymization rules in the GitHub Issues section of CLAUDE.md. Use public evidence or independently developed material suitable for public review. Keep restricted research outside the checkout; removing links or attribution does not make internal findings publishable.

Ground the idea

Establish the concrete user problem and investigate enough context to make the direction credible:

• Check VISION.md for product fit and CONSTITUTION.md for invariants.
• Read relevant code and existing command help to understand the current behavior and nearby capabilities.
• Search existing issues and PRs for duplicates or decisions to reuse.
• Investigate relevant public APIs or dependencies where they affect feasibility. Scale research to the proposal; state unknown API readiness, permissions, data availability or other feasibility gaps explicitly.

Separate observed facts, user-reported needs and proposed behavior. When evidence contradicts the idea or an invariant prevents it, explain the conflict and reshape the proposal before drafting. A proposal can carry unresolved feasibility questions for maintainer review.