propose

The developer wants to capture an idea as a proposal. Invoke the draft-proposal skill.

If the developer included a one-line description in $ARGUMENTS, use it as the seed for the proposal title and the description: frontmatter — but still confirm the full content with them before drafting (you'll need to collect the four required fields: problem, sketch of approach, effort, owner).

If $ARGUMENTS is empty, derive the candidate proposal from the recent conversation: identify the most recent feature/infra/process idea that came up, restate it back to the developer in one or two sentences with your best guess at category and effort, and only proceed after they confirm or wordsmith.

Disambiguate from team rules. If the idea is really a coding convention or generic team standard (not a thing to build), invoke /share-rule / the propose-team-rule skill instead. The two are mutually exclusive — same insight should never end up as both.

The skill handles the rest — git worktree isolation, file drafting, index update, branch creation, push, and either PR or direct merge. Surface the resulting URL to the developer when done.