wikitool-knowledge-interview

name	wikitool-knowledge-interview
description	Interview users to shape an article's intent, scope, and angle and surface what they know, before research and drafting.

Skill: wikitool-knowledge-interview

Thin wrapper for the human knowledge interview faculty that supports wikitool authoring.

Use normal reasoning, ordinary shell/file tools, and direct editing by default. Verify wikitool commands against wikitool --help, wikitool <command> --help, and docs/wikitool/reference.md. The conversational loop belongs to the agent; the Rust CLI owns deterministic ledger creation, validation, summaries, audits, and structured open-item logging through wikitool knowledge interview init|validate|show|audit|open-item.

Read writing_context/interview_playbook.md before using this skill. Start with a compact scout: wikitool knowledge article-start "<Topic>" --intent new|expand|audit|refresh --format json --view brief, plus a cursory wiki/source search when useful. knowledge interview init also runs the scout itself: it seeds the brief with a tool-written Scout Context section and returns an evidence-grounded question_agenda - adapt those areas conversationally rather than reading them as a script, and use --no-scout when a blank brief is wanted. If the user provides documents, links, screenshots, transcripts, notes, or source excerpts, read them before narrowing the interview and use them to ask better questions. Then interview to the depth needed to improve the article or review; there is no fixed round count.

Interviewing is an optional, conversational lane, not a rigid gate - but for real article work it is the normal move. Its job is direction: set the article's intent, scope, and angle by finding out what the person actually wants written, not only what they know that the public record lacks. Reach for it by default on new articles and substantial expansions, including well-documented subjects, because Remilia Wiki writes every subject from its own perspective and the interview is how that angle gets set - a generic entry on the manul becomes the manul as this wiki would frame it. Skip it for mechanical lint, link, sync, source-fetch, or validation tasks, on an explicit opt-out, or for tiny edits. When you do interview, begin with a broad freeform prompt that asks the user what the article should be about and why, what they know, what details or sources may not be online, what outsiders misunderstand, and what should not be overstated. Reflect the scope back in neutral wiki language, ask adaptive follow-ups based on article-shaping gaps, and continue while new answers materially improve scope, terminology, date/order disambiguation, source strategy, section planning, or risk.

When the interview yields reusable knowledge, write a brief under .wikitool/interviews/<Title-safe>/<YYYYMMDDTHHMMSSZ>.brief.md. Treat the brief as working notes, not article prose or citation evidence. A quality-gated human statement can become article prose as reasonable truth; cite when research surfaces a source or the claim is external, contested, or the kind that needs one. A mechanically valid brief is not proof that the interview is complete or that the draft is acceptable. For Remilia Wiki, corroboration may be a target-wiki record, hosted artifact, first-party source, archived primary record, creator-published statement, or target-wiki source note; do not require outside secondary coverage when the wiki is preserving niche subcultural history for the first time. Do not force adjacent subjects into a "relationship to Remilia" frame. Ask for the editorial vantage, adjacency, or canon purpose, then write the subject as itself unless a direct Remilia/Milady/community relationship is real and article-shaping.

Use wikitool knowledge interview init "<Topic>" --intent new|expand|audit|refresh --format json to create the timestamped brief and sidecars, then fill the brief from the interview. Before drafting from it, run wikitool knowledge interview validate PATH --format json; use wikitool knowledge interview show PATH --view brief --format json and wikitool knowledge interview audit --view brief --format json for handoff and ledger checks. Use wikitool knowledge interview open-item add PATH --kind rejected-source|inaccessible-source|missing-source|do-not-assert|scope-unresolved --text "..." to record unresolved research work, negative evidence, or a do-not-assert hold without turning it into article prose, and open-item update PATH --item-id ID --status resolved to transition a logged item. Pass validated briefs to wikitool knowledge article-start "<Topic>" --brief-path PATH --format json --view brief and wikitool review --brief-path PATH --format json --view brief --summary "..." when the interview should inform research planning or review.

Before drafting, run a short interviewer/critic pass: identify what would make the article thin, duplicative, unsourced, wrongly framed, or missing the user's actual knowledge. If that critique raises article-shaping gaps, ask another interview round instead of closing on a checklist.