content-interview

Content Interview

Interview the user to produce content for the resume vault. The argument $ARGUMENTS may specify the content type and a brief description (e.g., "experience my role at Hyperion" or "showcase my workflow-api repo").

Phase 0: Determine content type

If $ARGUMENTS specifies the type, use it. Otherwise ask:

What are we capturing?

1. Experience — a job role (produces content/experience/{id}.md)
2. Showcase — a repo or side project you want to demo (appends to content/showcases.md)
3. Project — a notable project or community contribution (appends to content/projects.md)

Do not proceed until the type is clear.

Phase 0b: Detect existing content (extend mode)

After determining the content type, check whether an entry already exists:

• Experience: Search content/experience/*.md for a file matching the company name or description from $ARGUMENTS. Read the file.
• Showcase: Search content/showcases.md for a matching ## {Name} or id: entry. Read the relevant section.
• Project: Search content/projects.md for a matching ## {Name} entry.

If existing content is found:

1. Present a summary to the user:

   I found an existing entry for {name} in {file path}:

   • Narrative: {sentence count} sentences, {paragraph count} paragraphs
   • Sections: {list of ## headings with bullet counts, e.g., "Achievements (6), Leadership & Mentoring (3)"}
   • Technologies: {count} listed

   Do you want to extend this entry (add sections, fill gaps, add bullets) or start a new entry (e.g., a different role at the same company)?

2. If the user chooses extend, proceed to Phase 1 in extend mode (gap-filling questions).

3. If the user chooses start new, proceed to Phase 1 as normal (full interview).

If no existing content is found: proceed to Phase 1 as normal.

Phase 0c: Read the lenses before you interview

Do this for every experience interview, new or extend. It is what turns one job into several resumes.