/write
Turn a rough need or existing item into one confirmed, provider-backed ticket.
/write turns a rough need or an existing item into one confirmed,
provider-backed ticket. It asks only for missing context, routes qualification
to the best-fit writing skill when needed, and never saves without human
approval.
How /write shapes an item
01 · AssistedResolveCreate or update, provider, and target.
Questioning loop
02 · AssistedAsk one focused questionChallenge only what is relevant and still unclear.
HumanAnswerAdd the missing decision or source.
More context neededHumanConfirm understandingValidate the outcome before drafting.
Revision loop
03 · AssistedDraft one itemPresent one complete proposal.
HumanReview proposalSave it or request an adjustment.
Adjust item04 · WorkflowCreate or update itemPersist the confirmed title and body, then apply
agent-shaped.Skills used under the hood
Qualification loads at most one skill at a time. When none of these conditions
applies, /write qualifies the need directly without loading a skill.
Intent is unclearinterview-me Ask focused questions until the actual need is understood.Direction is openidea-refine Explore and narrow an idea before committing to a direction.Decisions need challenginggrilling Test assumptions, risks, and unsupported choices.Specification format acceptedto-spec Structure the result as a specification after explicit opt-in.
What /write does
| 1 | Resolve | Infer create or update, resolve the configured provider, then find the destination or existing item. |
|---|---|---|
| 2 | Qualify | Ask only for decisions that are still missing. Use at most one best-fit writing skill when it helps. |
| 3 | Understand | For qualified needs, require human confirmation of the concise understanding before drafting. |
| 4 | Draft | Present one complete item, revise it when requested, and wait for an explicit Save item decision. |
| 5 | Save | Create or update the item, apply agent-shaped, and report the provider result. |