General Work
- State the outcome, format, audience, constraints, and acceptance criteria.
- If a workspace exists, reference sources with
@; otherwise require explicit assumptions and an input checklist. - Ask for a plan before execution; keep Manual approve for writes.
- Review each approval card’s tool, target, and parameters.
- Open the output and verify every claim against its cited source.
Copyable prompt
I need a one-page product review brief. First list facts to verify, conflicts, and missing information, then provide three options, a recommendation, risks, and next steps. No workspace or source files are selected yet: do not invent internal data. Label assumptions as public context and turn missing inputs into a checklist. Use Markdown headings and tables.


What is different in Wordless
Section titled “What is different in Wordless”Instead of returning an opaque chat answer, Wordless keeps references, approvals, file writes, and success/failure states in one thread. Start with no context, then add @ files, $ Skills, and explicit approval constraints only when the task needs them.
Practical scenarios
Section titled “Practical scenarios”| Scenario | Input | Verifiable result |
|---|---|---|
| No-context planning | A written goal without a workspace | Assumptions and missing inputs remain separate |
| Multi-file decision brief | @ brief and notes folder |
Every key conclusion cites a source path |
| Plan written to disk | Goal plus output path | A reviewed write with visible completion state |