ds-continuity

Included with Lifetime

$97 forever

Death & Sourdough series continuity checker. MANDATORY before writing or editing ANY prose chapter for the Death & Sourdough project. Ensures cross-referencing of established facts (character details, locations, timeline, objects, quoted text, relationship dynamics) against the Continuity Bible, and updates the bible after writing. Trigger whenever: (1) writing a new chapter, (2) revising or fleshing out an existing chapter, (3) adding new characters, locations, or named details to the prose.

Writing & Docs

What this skill does

# Death & Sourdough Continuity Checker

## Workflow

Writing or editing any chapter involves these steps:

1. **Pre-write: Load continuity context**
- Read `Death_and_Sourdough_Continuity_Bible.md` in the project folder
- Read `A_Crust_of_Suspicion_Chapter_Breakdown.md` for the target chapter's planned beats
- Read `Death_and_Sourdough_Dramatis_Personae.md` for character reference
- If the chapter references events from earlier chapters, read those chapters

2. **During writing: Cross-reference established facts**
- Before using any character name, check the bible for established spelling and details
- Before describing any location, check the bible for established physical details
- Before quoting or paraphrasing Gran's journal, check the bible for verbatim established quotes
- Before referencing timeline or days, check the bible's timeline table
- Before writing relationship dialogue, check the bible's relationship dynamics section
- Before describing baking, check the baking progress tracker for what has been established

3. **Post-write: Update the continuity bible**
- Add any new characters introduced (with physical descriptions, names, roles)
- Add any new locations or location details established
- Add any new Gran's journal quotes (verbatim)
- Update the timeline table with new events
- Update the baking progress tracker
- Update relationship dynamics with new significant beats
- Add any new backstory breadcrumbs planted
- Add any new unresolved threads introduced
- Flag any potential discrepancies discovered

## What to Check

**Names:** Full names, spellings, titles. Geoffrey's niece is Claire Finch. The parish council chair is Margaret Aldridge (not Patricia). Margot's surname is Prescott (never Chen).

**Numbers:** Ages, dates, durations, word counts, distances. Gran was born 1938. The bakery was established 1962. Check years of service, days elapsed, times of day.

**Physical details:** What characters look like, what they wear, what buildings contain. These must not change between chapters unless the change is deliberate and noted.

**Inscriptions and signs:** The bakery sign, Gran's headstone, "Mother"'s label, pub signs. These are fixed text. Copy verbatim from the bible, never paraphrase or alter.

**Quoted journal text:** Gran's journal passages are established canon. Never alter previously quoted text. New passages must not contradict established ones.

**Timeline:** What day it is, how many days have passed, what has happened in what order. Cross-reference the timeline table before writing any temporal reference.

## References

The Continuity Bible lives at: `Death_and_Sourdough_Continuity_Bible.md` in the project folder. It is a living document and must be updated after every chapter.

Files: 3

Size: 4.4 KB

Complexity: 14/100

Category: Writing & Docs

Source: https://github.com/rawveg/skillsforge-marketplace/tree/main/ds-continuity

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts