story-import

You are running /story-import. This is a one-shot migration tool that converts a legacy STAR-stories markdown file into the canonical schema.

The user's working directory is $CLAUDE_PROJECT_DIR. Paths in the command instructions below are relative to it unless prefixed with ~/ or /.

Step 1 — Resolve source file

If the user supplied an argument ($ARGUMENTS), treat it as the source path. Resolve ~/ if present.

If no argument, ask the user for the source file path. Suggest scanning $CLAUDE_PROJECT_DIR for *-star-stories.md and listing matches; let user pick.

If the resolved path doesn't exist or isn't readable: report the error and stop.

Step 2 — Read the source

Use the Read tool on the resolved path. Limit to the file's full length (no offset).

Step 3 — Parse the source

Identify these sections:

• Title: the H1 heading. Use this as the canonical title; slugify to kebab-case for the canonical id (e.g., "Acme UI Components Library — Netflix JSF" → strip company-specific suffixes if obvious, then slugify → acme-ui-library).
• Core Facts: any ## Core Facts section (or close variant like "Core Facts (memorize these...)").
• Key Metrics: any ## Key Metrics section. Extract bullet items into a flat list for frontmatter metrics:. If this section is absent, emit metrics: [] and continue; do NOT fall back to Step 6.
• Approaches: every ## APPROACH X: <Theme> heading. Slugify <Theme> to derive an approach-slug (e.g., "The Platform Builder" → platform-builder).
  • Slugification rules (apply to both approach-slug and theme-slug for determinism on re-runs):
    1. Lowercase.
    2. Strip leading articles: "the", "a", "an".
    3. Replace whitespace and punctuation (em-dashes, slashes, commas, etc.) with single hyphens.
    4. Collapse consecutive hyphens.
    5. Trim hyphens from edges.
• Variants: every ### Q: <question> heading under an approach. For each:
  • Slugify the question's main theme (the noun-phrase, not the full question) to derive a theme-slug (apply the slugification rules above).
  • Variant id = <approach-slug>-<theme-slug> (e.g., platform-driving-adoption).
  • Capture the bold-key blocks: **Situation:**, **Task:**, **Action:**, **Result:**. Preserve their multi-paragraph content verbatim. If any of the four STAR blocks is absent for a variant, write the field with the value (not captured — fill in manually) and include the variant id + missing field in the Step 7 summary's "themes to refine" or a new "gaps to fill" section.