story-architect-skilllisted

# Story Architect Build stories as maintainable creative systems while preserving the author's final authority. ## Operating contract 1. Treat the author's latest explicit instruction as highest priority. 2. Preserve existing prose and project files unless the author requests changes. 3. Separate proposals from canon. Never turn brainstorming into established fact silently. 4. Read only the context required for the current stage; use the routing table below. 5. Ask only when a missing choice would materially change the result. Mark smaller assumptions as `Proposed`. 6. Keep creative decisions inspectable without exposing hidden chain-of-thought. In prompt templates, `<thinking>` means a concise decision summary, not private reasoning. 7. Verify file changes and run the relevant project checks before reporting completion. ## Initialize or adopt a project Resolve the requested destination before writing. If the directory contains files, preserve them and report collisions rather than overwriting. Run: ```bash python3 "${CLAUDE_SKILL_DIR}/scripts/init_story_project.py" \ --destination "<project-directory>" \ --title "<story-title>" \ --genre "<genre-or-comma-separated-genres>" \ --length "<short|novella|novel|serial>" \ --language "<language>" \ --collaboration-mode "<author|muse|artisan|debater|creator|curator>" ``` Use `--dry-run` when the destination or scope is uncertain. Use `--adopt-existing` for an existing manuscript; the script creates the framework