Claude Interactive Documentation Workflow skill
A documentation-first method for Claude Code: the /interview skill, document and plan templates and handoff rules.
- 105 ★ on the repository
- Last commit
Minimal access
Why this level
- The skill only runs a dialogue and writes documentation files into the repository; no external services.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/claude-interactive-documentation-workflowDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill only runs a dialogue and writes documentation files into the repository; no external services.
This is third-party code. Review the repository files before installing.
What it does
The repository describes a feature workflow: interview or investigation, then documentation, then a plan and only then implementation. Each stage has a guide with checkpoints. The `/interview` skill installed in the project runs a four-pass questioning and prepares the basis for a document. The rest lives in `documentation/`: rules for writing plans, handing off work, reviewing investigations and testing on a live system, a ready user-level rules template and a recipe for adopting the method in another repository.
Who it is for. Developers running projects with Claude Code who want documents and plans that models and people can still follow months later.
Good fit when
- Before a large feature requirements are gathered by interview.
- Raw investigation notes are turned into a document and a plan.
- Work is handed to another session and a structured handoff file is needed.
- The method is to be adopted in your own repository from a ready recipe.
Not a fit when
- A quick one-line fix without documents is needed.
- The team is not ready to maintain separate documentation and plan files.
- You want a skill without examples from someone else's project.
Example request
Interview me about an email sign-in feature and build a document from the answers using the rules in `documentation/`.Limitations
Examples come from a real project (computer vision, vessel tracking) and the author left them on purpose: terms and prefixes must be replaced with your own. The license is detected as NOASSERTION, so check reuse terms in the `LICENSE` file. The last commit dates from July 2026. The case-study figures are the author's own. The method demands discipline: without regular updates, documents and plans drift away from the code.
How to disable. Delete `.claude/skills/interview` from the project or from `~/.claude/skills` and remove the methodology lines added to `.claude/CLAUDE.md` by hand.
FAQ
How do I start an interview?
In Claude Code run `/interview` with a topic, for example `/interview user authentication system`. The skill is already in the project.
How do I add the skill to my project?
Create `.claude/skills/interview` and copy `documentation/general_interview_methodology_skill.md` there as `SKILL.md`. For all projects copy it into `~/.claude/skills`.
What is an investigation here?
A loose gathering of facts about something existing or broken. When mature, it feeds the same document and plan as an interview.
Does the method work with other models?
The author says the approach suits any model, but the `/interview` skill is built for Claude Code.
Where do I start adopting it?
With `documentation/general_methodology_adoption_recipe.md`. It is the single reference for what to copy, where to put it and what to paste into `.claude/CLAUDE.md`.
Discussion
No questions or reviews yet.
Related
SkillsClaude Code course repository for product managers: 55 skills, slash commands, subagents and demo apps with module assignments
Claude Code Toolkit (robertguss)
Claude Code Toolkit
A set of Claude Code skills and hooks: brainstorming, worker-led project leadership, a wiki, and a book pipeline.
100 Claude Code recipes for office work and six ready skills: meeting notes, reports, summaries and data cleanup
A skill that keeps project memory in plain Markdown files: session logs, a wiki, rules, a to-do list and a note on where to resume
A Claude Code plugin that catches your corrections in chat and, after review, writes them into CLAUDE.md and AGENTS.md
A CLAUDE.md and AGENTS.md file with seven principles: the agent frames the problem and scope before it writes code
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Interactive Documentation Workflow (this card) | no | 105 | |
| Spec-Driven Development | no | 158 | proposes a specification approach; this one adds interviews, investigations and handoff rules |
| Interview Skills | no | 402 | teaches interviewing for another purpose; here the interview prepares feature documentation and a plan |
README in short
By the author's account the method was used in three or more projects and extracted together with a case study based on git history. The adoption recipe is written for an agent.