Maintain narrative continuity in multi-turn roleplay sessions with world-state tracking.
npx skills add https://github.com/tta-lab/ttal-cli --skill sp-roleplay
Please help me install this Agent Skill. Skill: sp-roleplay Source: https://github.com/tta-lab/ttal-cli/tree/main/skills/sp-roleplay Command: npx skills add https://github.com/tta-lab/ttal-cli --skill sp-roleplay
sp-roleplay prevents long collaborative fiction from losing continuity by forcing you to track world-state, character positions, voice, canon-uncertain facts, and invented-mechanism constraints turn-by-turn.
Use sp-roleplay for a multi-turn scene by creating a roleplay scratch file from scratch.template.md, filling Phase 0 (Resolution, Cast register, Per-character state board, Term glossary, Canon hedges, Mechanism commits) before writing turn 1, and then updating the turn-by-turn log plus state board after every turn.
High-intent search queries and answers about installing and using this skill.
To maintain narrative continuity in long collaborative fiction, use a resolution-first scaffolding approach with an append-only world-state register that tracks cast, per-character state, and canon hedges before writing turn 1.
Resolution-first scaffolding in roleplay requires drafting a resolution paragraph and populating a world-state register before writing turn 1, preventing the strong open but weak end failure mode in scenes longer than five turns.
To stop NPC dialogue contradictions, enforce per-turn mechanical discipline by re-reading the latest state board and cross-checking NPC dialogue against persistent artifacts before appending the new turn to the collaborative fiction log.
You should run consistency audits every five turns during a long roleplay scene to catch drift, contradictions, and plot stance problems, applying out-of-frame corrections to maintain strict narrative continuity.
To lock invented magic or time-travel parameters in collaborative fiction, commit mechanism constraints early in a Phase 0 scratch template and enforce append-only tracking to prevent parameter drift across multi-turn roleplay sessions.
Yes, you need a scratch template to track canon hedges and character state in roleplay, as it forces Phase 0 population of resolution, cast register, glossary, and mechanism commits before writing the first turn to ensure continuity.
wanikuaOK, I'll do that.
tacodaDetect policy drift and strict violations in vendored policy files.
jamesrochabrunGenerate rule-based trading plans with entry, exit, and risk management rules.
magnus919Create and analyze settings, scenes, and visual briefs using William Gibson's Sprawl fiction logic.
