interview-style-doc-building
Build structured strategy documents by asking one question at a time and patching the file.
Human ResourcesProject & Program ManagementManagement & Team LeadershipOffice & Administrationdocumentationinterviewplanning
Interview-Style Doc Building
The user's preferred mode for creating durable strategic docs. AI does NOT propose content — AI asks one question, the user answers, AI patches the file, AI asks the next question. The file IS the conversation's output, updated incrementally.
When to Use
- Building a new SSOT file (life priorities, life vision, principles, frameworks, ranked lists).
- Filling out a structured doc the user explicitly wants to author themselves.
- Quarterly/annual reviews where the user's words go into the file.
NOT for: day planning (use day-plan), task triage (organize-tasks), or anything where AI proposes content first.
The Loop
- Create the file with a skeleton (header, sections, "to be filled in" placeholders). Single
write_filefor the new file. After this, NEVER overwrite — onlypatch. - Ask ONE question. Concise. Specific. Single-faceted. Open-ended where possible.
- Wait for the answer. Don't ask the next question yet.
- Patch the file with the user's answer in the correct section.
- Re-ask — next question, or follow-up if the answer was incomplete.
- Repeat until the file is complete.
Hard Rules
- One question at a time. Never dump multiple questions in a single message. The user has flagged this.
- Patch, don't overwrite. After the initial skeleton, use
patchfor every update. Never `write_
Subscribers only
The full skill, its 1 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | davidondrej/skills |
|---|---|
| License | MIT |
| Risk label | critical ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md |
| Added | 2026-07-07 |
Related skills
anywrite
Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.
ask-matt
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
box-automation
Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit.
brain-to-docs
Interview the user to turn project vision and decisions into README and ADR documentation.
cal-com-automation
Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.
calendly-automation
Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.
