How the STAR+R Story Bank Accumulates Across Evaluations in Career-Ops

The STAR+R story bank grows by automatically appending new interview stories generated during each Oferta mode evaluation, checking for duplicates before adding entries to interview-prep/story-bank.md to build a reusable master set over time.

The santifer/career-ops repository manages interview preparation through a persistent Story Bank that accumulates high-impact narratives every time you evaluate a job offer. This self-updating system ensures that each STAR+R story you create remains available for future interviews, eliminating the need to rewrite accomplishments for every new application.

The Accumulation Mechanism

The story bank operates as a cumulative markdown ledger that expands through a systematic three-phase process during every full job evaluation.

Generation of New Stories in Block F (Oferta Mode)

Each time you run the Oferta mode (the full A-G evaluation workflow), the system generates 6-10 STAR+R stories specifically tailored to the current job description's requirements. In modes/oferta.md, Block F creates a structured table containing the Situation, Task, Action, Result, and a Reflection column documenting lessons learned (lines 66-73).

The Reflection component distinguishes STAR+R from standard STAR methodology, capturing insights about what you learned from each experience. This generation happens automatically based on the requirements analysis performed earlier in the evaluation workflow.

Duplicate Detection and Append Logic

After Block F generates the stories, the mode executes a check-and-append routine to prevent redundancy. According to lines 74-75 of modes/oferta.md, the system verifies whether interview-prep/story-bank.md already contains each generated story.

If a story is absent from the bank, the mode automatically appends it to the file. This deduplication check ensures that repeated evaluations of similar roles do not clutter your bank with redundant entries, maintaining a lean collection of unique, high-value narratives.

Cumulative Growth Over Time

Because this check occurs on every evaluation, the bank gradually accumulates a reusable collection of 5-10 "master" stories. The header of interview-prep/story-bank.md (lines 1-8) explicitly documents this accumulation process, explaining how repeated evaluations build a comprehensive repository of verified accomplishments.

Rather than starting fresh for each job application, you maintain a growing library of proven stories that demonstrate consistent competence across multiple contexts and roles.

File Structure and Data Contract

The accumulation system relies on three key components defined in the repository structure:

• interview-prep/story-bank.md — Serves as the central storage for cumulative STAR+R stories. The file includes placeholder comments indicating where new entries are inserted during evaluations.
• modes/oferta.md — Contains both the generation logic in Block F and the append instructions that trigger after story creation.
• DATA_CONTRACT.md — Declares interview-prep/story-bank.md as the system-level data contract for accumulated stories, ensuring consistent read/write operations across modes.

The following example shows the exact markdown format the engine writes into the bank:

### [Leadership] Leading a cross‑team migration

**Source:** Report #042 — Acme Corp — Senior Engineer
**S (Situation):** The legacy monolith was causing frequent outages.
**T (Task):** Migrate the service to a micro‑services architecture within 3 months.
**A (Action):** Designed the target architecture, coordinated three squads, set CI/CD pipelines, and introduced feature flags.
**R (Result):** 40 % reduction in incidents, 30 % faster deployments, and saved $200k in operational costs.
**Reflection:** Learned the importance of incremental rollout and stakeholder communication.
**Best for questions about:** “Tell me about a time you led a complex technical change.”

Reusing Stories for Future Interviews

When evaluating a new job opportunity, the system reads the existing story bank to accelerate preparation. The Interview-Prep mode (modes/interview-prep.md, lines 9-14) accesses the accumulated stories and maps the most relevant entries to the new job description's requirements.

This retrieval process saves you from rewriting the same narratives repeatedly. Instead of creating new stories from scratch, you adapt existing master stories from the bank to fit specific interview questions, ensuring consistency while reducing preparation time.

Summary

• Automatic accumulation: The Oferta mode generates 6-10 STAR+R stories during Block F and appends them to interview-prep/story-bank.md after each evaluation.
• Duplicate prevention: The system checks existing entries before appending, ensuring the bank contains only unique stories.
• Persistent storage: Stories remain available across evaluations, creating a reusable library of 5-10 master narratives.
• Cross-mode integration: The Interview-Prep mode reads the bank to suggest relevant stories for new job applications.
• Structured format: Each entry includes Situation, Task, Action, Result, and Reflection components for comprehensive interview preparation.

Frequently Asked Questions

What is the STAR+R format?

STAR+R is an enhanced version of the STAR (Situation, Task, Action, Result) interview response framework that adds a Reflection component. This additional field documents what you learned from the experience, providing depth for behavioral interview questions about growth and adaptability. According to modes/oferta.md, the Reflection column appears in the Block F story generation table (lines 66-73).

How does the system prevent duplicate stories?

The Oferta mode includes a verification step that checks interview-prep/story-bank.md before appending new entries. As specified in lines 74-75 of modes/oferta.md, the system only appends stories that do not already exist in the bank. This check runs automatically after Block F generates the new story table for the current evaluation.

Can I manually edit the story bank?

Yes. interview-prep/story-bank.md is a standard markdown file that you can edit directly. The file includes header comments explaining the format and accumulation process (lines 1-8), and the system appends new entries below existing content. Manual editing allows you to refine stories or add entries from evaluations performed outside the automated workflow.

How many stories should the bank contain?

The system is designed to accumulate 5-10 master stories over time. According to the Oferta mode documentation, this range provides sufficient variety to adapt to most interview questions while remaining manageable. The Reflection components in STAR+R format allow these 5-10 stories to be reshaped for different contexts, maximizing their utility across multiple job applications.

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