interview-import

To import planning artifacts for interview prep, run a recursive directory scan targeting SPEC.md, PHASES.md, and RESEARCH.md files. The tool extracts feature titles from the first H1 heading and logs centralized entries into a dedicated interview feature log.

Importing planning artifacts repeatedly should not create duplicates because the process uses content hashing for idempotent updates. If a file's content hash matches a previous import, the system skips it, ensuring your interview feature log remains clean during re-imports.

You can filter planning artifacts using optional artifact_types parameters and execute a dry_run to preview changes. The dry run scans directories recursively without writing to the feature log, while filters restrict imports to specific SPEC.md, PHASES.md, or RESEARCH.md files.

The best way to consolidate project specs for interview readiness is running an automated recursive directory scan across repositories. It assembles scattered SPEC.md, PHASES.md, and RESEARCH.md files into a centralized features.jsonl log with tracked import history.

Imported interview features are stored in ~/.interview-prep/features.jsonl after scanning project directories. The system also maintains an import-index.jsonl file recording the complete import history and content hashes for idempotent tracking.

You need a first H1 heading in your planning artifacts for the import to extract feature titles effectively. The system relies on these H1 headings to generate quick review titles when creating centralized interview feature entries from your specs.