wewrite-write — Task Brief, Evidence and First Draft
Prerequisites
Run
to read the current task. If there is no task but the user has provided a topic, create it in
mode; if there is no topic, redirect to
. This module only writes
,
, and
;
is generated by the review module after approval.
Read
; if it does not exist, execute
first. Read custom personas
{home}/personas/<name>.yaml
, built-in
in order of priority, and finally fall back to
. Personas only control expression preferences and cannot override facts, personal materials, and article task briefs.
Run
wewrite run step write in_progress
upon entry.
3. Article Tasks and Materials
Read in full:
text
读取: {skill_dir}/references/article-brief.md
读取: {skill_dir}/references/editorial-quality.md
读取: {skill_dir}/references/frameworks-quick.md
读取: {skill_dir}/references/content-enhance.md
3.1 Define the Article First
Clarify the target audience, reading context, real problems, takeaways, core judgments, added value, applicable boundaries, and the strongest counterarguments. Select the most suitable type from pain points, stories, checklists, comparisons, hot topic interpretations, opinions, and retrospectives. Write the results to
, and do not jump directly to the main text.
Also record the personal materials for this session: only experiences, observations, or exact words explicitly provided by the user in the current task are considered usable. When
personal_materials.available=false
, first-person judgments can be written, but fabricating personal experiences, friends/colleagues, interviews, conversations, time/place, actions, and sensory scenes is prohibited. When the persona requires a story or personal opening, use an observation, question, or judgment opening instead.
3.2 Build Claims and Evidence
Search around the 3-6 claims that the article really needs to prove. Each specific data, quote, case, or time-sensitive fact included in the article must be verified on the original page and recorded immediately:
bash
wewrite sources add --url "{原始页面}" --title "{标题}" --publisher "{发布方}" \
--published-at "{日期}" --claim "{该页面支持的具体主张}" --status verified
Prioritize original reports, official documentation, and information from the parties involved. User materials are marked as
; search summaries, model memories, or sample essays must not be marked as
; in particular, model memories must not be marked as
. Write facts, inferences, opinions, and user experiences into
, citing the source numbers from
.
claims must not be included in the first draft.
When search is unavailable, only write analyses that do not rely on the latest data and bounded judgments; delete unverifiable numbers, quotes, and "studies show" statements, and record the downgrade in the task.
3.3 Safety Enhancement
Supplement the current framework with new angles, action conditions, real details, or decision-making criteria according to
. Enhanced content must also be added to the claim and source list. If materials are insufficient, narrow down the claims or change the framework; forced reversals, added stories, or fabricated "inside information" are prohibited.
4. Write the First Draft
First run
wewrite learn-edits --summarize --json
to get rules that are still valid, and do not directly trust the cached scores of the old
. Only use rules that match the current content_type/framework/persona: only rules with
are hard constraints, the rest are for reference only; global structure or tone rules that are only single modifications must not be enforced.
Read up to 2 relevant sample essays from the sample library:
- Sample essays marked and created/modified by the user themselves can help calibrate tone and structure.
- Third-party or old sample essays lacking metadata are all treated as third-party, and can only be referenced for rhythm and structure.
- No sample essay may provide reusable personal experiences, characters, conversations, specific details, opinions, or sentences.
Writing requirements:
- The title should be accurate, with a clear target audience and benefit points; the main text is usually 1200-2500 words, which can be adjusted according to the task brief.
- The opening should address the reader's problem or core judgment as soon as possible; each section serves and the corresponding claim.
- Clearly distinguish between facts, inferences, and personal opinions; include counterarguments and applicable boundaries, and do not use consensus or clichés to pad word count.
- The account's tone comes from style, persona, and filtered learning results, but content and evidence always take priority.
- Fabricating personal experiences, identities, interviews, numbers, evaluations, quotes, and details not present in sources is prohibited.
If
flags.use_writer_model=true
, call
with
,
, source ledger, style, and the above boundaries as complete input, and output to
; if it fails, the current Agent writes directly. Otherwise, write the first draft directly. In both cases, read through the entire draft according to the task brief and claim list, and correct attribution, repetition, jumps, and out-of-bounds content.
Update the task after completion:
bash
wewrite run update --patch '{"framework":"...","enhance_strategy":"...","persona":"...","word_count":0,"provenance":{"verified_sources":0,"unverified_sources":0,"exemplars":[],"playbook_rules":[]}}'
wewrite run step write completed
When called independently, inform the user of the paths to the first draft, task brief, and claim list, and recommend proceeding with
; do not refer to the first draft as a reviewed final article.