How the Career-Ops Interview Story Bank Accumulates STAR+Reflection Stories Across Evaluations

Career-Ops automatically appends new STAR+Reflection stories to interview-prep/story-bank.md every time the Offer Evaluation mode (/career-ops oferta) finishes generating a Block F interview plan.

The santifer/career-ops repository automates interview preparation by maintaining a persistent interview story bank that accumulates STAR+Reflection stories across evaluations. Each time a candidate runs a job analysis, the system parses the output and stores unique behavioral narratives for future reuse. This ensures candidates build a curated, reusable library without manual copying.

How Block F in modes/oferta.md Defines STAR+Reflection Stories

In modes/oferta.md, the report template specifies Block F as the interview-plan section that lists 6–10 STAR+Reflection stories matched to the job description requirements. The template includes an explicit instruction at lines 78–88: if interview-prep/story-bank.md exists, check whether the generated stories are already present, and append any new ones.

Persistent Storage in interview-prep/story-bank.md

The file interview-prep/story-bank.md acts as the permanent markdown store for all accumulated narratives. According to the header commentary at lines 3–8, every evaluation that produces Block F will append new stories to this file so the candidate can reuse them for future interviews.

File-System Append Logic in update-system.mjs

The actual write operation is coordinated by the report-generation script and executed by the update-system helper. In update-system.mjs at line 152, the helper references the exact path to story-bank.md and performs the file-system write when a new report is saved.

The generation script parses the Block F table, extracts story rows that are not already present in the bank, and appends them to the end of the file. This deduplication check preserves existing content and prevents duplicate entries.

Report-Generation Pseudocode

The following pseudocode illustrates how the report-generation step reads the bank, checks for existing titles, and appends missing STAR+Reflection stories:

// Pseudocode from the report-generation step
const storyBankPath = 'interview-prep/story-bank.md';
const blockFStories = extractBlockF(report);  // rows from Block F table

let storyBank = await readFile(storyBankPath);
for (const story of blockFStories) {
  if (!storyBank.includes(story.title)) {
    storyBank += formatStoryForBank(story);
  }
}
await writeFile(storyBankPath, storyBank);

Complete Workflow: From Job URL to Curated Story Bank

1. The user runs /career-ops oferta <job-url> and the AI generates a full evaluation report.
2. Block F contains 6–10 new STAR+Reflection stories tailored to the job description.
3. The generation script reads interview-prep/story-bank.md and checks for existing titles.
4. Missing stories are appended to the end of the file, preserving existing content.
5. Over multiple evaluations, the bank consolidates into a curated set of 5–10 master stories that can be combined to answer any behavioral question.

Summary

• Block F in modes/oferta.md (lines 78–88) defines the STAR+Reflection stories generated for each job evaluation.
• interview-prep/story-bank.md (lines 3–8) serves as the persistent markdown file that stores accumulated narratives across all evaluations.
• update-system.mjs (line 152) coordinates the file-system append operation when new reports are created.
• The deduplication logic checks story titles to prevent duplicates and preserve existing content.
• Candidates eventually build a reusable master set of 5–10 interview stories without manual copying.

Frequently Asked Questions

How does Career-Ops prevent duplicate stories in the story bank?

The report-generation script checks each story title from Block F against the existing contents of interview-prep/story-bank.md. If a story title is already present, the script skips that entry and appends only new, unique narratives.

What triggers the append operation to the interview story bank?

The append operation triggers automatically when the Offer Evaluation mode (/career-ops oferta) finishes generating a report. Specifically, the completion of Block F in the output signals the update-system helper to perform the file write via update-system.mjs.

Can I manually edit interview-prep/story-bank.md without breaking the workflow?

Yes. Because the script performs a simple string-inclusion check on story titles and appends to the end of the file, manual edits to existing entries do not interfere with future automatic appends. The system preserves existing content and only adds missing stories.

How many stories should the story bank contain?

According to the modes/oferta.md template, each evaluation generates 6–10 STAR+Reflection stories for that specific job description. Over time, the bank typically consolidates into a curated set of 5–10 master stories that can be adapted to answer any behavioral interview question.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}