القائمة
Use when generating a weekly narrative that captures the week's real movement across life, work and creation in story form rather than as a report.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when running the weekly intelligence review. The AI briefs each engagement from live ecosystem data, the Sovereign speaks freely across 3 this-week and 2 next-week engagements, and the session closes with a Sovereign Command update.
Use when starting a session to initialize the AI interface with continuity checks, a live ecosystem orientation and approval-gated support sweep before any session work begins.
Use when archiving several ecosystem artifacts at once with per-artifact approval gates before any vault move executes.
Use when checking for published updates from the Sovereign Ecosystem GitHub repo and selectively applying only what you explicitly approve.
Use when a long-form manuscript (book chapter, ebook, multi-chapter playbook, long-form digital product) needs an editing pass to identify and remove AI writing tells against the Anti-AI Writing Patterns Codex. Triggered by the Sovereign after draft completion, by a Pending Plan handover map naming this skill at the edit phase, or by any post-draft state where AI-assisted prose needs the anti-pattern sweep before final review.
Use when updating a Pending Plan mid-arc with breadcrumbs, applicability changes, partial implementation notes and reconciliation-ready context.
استنادا إلى تصنيف SOC المهني
| name | weekly-story |
| description | Use when generating a weekly narrative that captures the week's real movement across life, work and creation in story form rather than as a report. |
| status | active |
| tier | operational |
| cadence | weekly (Fridays primary, Saturdays backup) |
Purpose: Generate a weekly narrative that captures the sovereign's real movement, across life, work and creation, in story form. Not a report. A narrative that reveals the shape of the week and the thread moving forward.
Trigger: Friday (primary), Saturday (backup). Typically runs after End-of-Week review, using that session's material as source data.
Output: Story file at Scriptorium/Weekly Stories/YYYY-MM-DD - [Title].md
Hard gate: Sovereign must explicitly confirm ("Save it" or equivalent) before the file is written.
Fire 6 workers simultaneously. Hold all results. Do not present yet.
Council Chamber/AI Interface/AI Interface Change Log.md and Vault (Archive)/Session Logs/ for this week, internal movement, decisions, completions, structural changesScriptorium/Weekly Stories/, extract recurring themes, open threads, named arcsAll workers complete before generation begins. If Worker 1 errors, pause and resolve before continuing.
From the combined worker results:
Do not present this step to the Sovereign. It is internal structuring only.
Write a cohesive weekly narrative in three parts:
Opening scene: one short paragraph. Place the reader inside a specific moment from this week that carries the week's central energy. Concrete, sensory where possible. Not a summary, a door in.
Week's chronicle: 3-5 paragraphs. Move through the week's major themes in sequence or by resonance (not necessarily chronological). Each paragraph carries one theme forward. Continuity threads from Worker 6 can be woven in without announcing them. The tone is earned and direct, not performed reflection.
Thread forward: one short paragraph. Name what is unresolved, what is building, what the sovereign is walking into next week. Not a task list. The living edge.
Frontmatter:
---
title: ""
date: YYYY-MM-DD
series: Weekly Stories
tags: [weekly-story, narrative]
---
Present the full story text to the Sovereign, frontmatter included.
Do not write the file yet.
Sovereign responds with one of:
On approval:
Scriptorium/Weekly Stories/YYYY-MM-DD - [Title].mdStatus is active. Authorized to generate and present without additional approval gates. The only hard gate is Step 4. Sovereign must explicitly confirm before the file is written.
Scriptorium/Weekly Stories/: output location(Empty, populated when execution mistakes occur during sessions.)