corepunch/zilscript

testing

Execute golden-path transcripts, wrong-attempt testing, save/reload persistence checks, and harden the automated parser-driven walkthrough

workflow-hints

Run specialized review passes (puzzle fairness, vocabulary audit, state audit) and maintain progressive parent-child hint UX

content-writing

Write player-facing prose, NPC dialogue trees, layered hints, and ensure every noun in text resolves through the parser

world-model

Translate design docs into a coherent simulation plan — validate puzzle fairness, audit parser vocabulary, and prevent softlocks before writing ZIL

accessibility-testing

Test target-audience approachability and accessibility through explicit player personas, fresh sessions, and evidence-based usability findings

bug-fixing

Fix technical and functional ZIL defects found during staged QA, including parser, object, exit, persistence, progression, and NPC failures

playtesting

Run blind functional play-throughs with @tester, collect player-visible evidence, and prepare functional regressions

quality-assurance

Coordinate independent technical, blind functional, artistic, and audience-accessibility release passes for a packaged ZIL adventure

zil-implementation

Implement game logic in ZIL with clean dungeon.zil / actions.zil split, clock daemons, and the critical rules that prevent compilation and gameplay bugs

artistic-review

Review a playable adventure for narrative architecture, genre craft, pacing, contrast, prose, puzzle-story integration, and ending quality

working-materials

Create the design artifacts (MAP, OBJECTS, PUZZLES, STORY_STATE, TRANSCRIPT_TESTS) that externalize world structure and puzzle logic

foundation-and-premise

Define the premise, tone, win/lose conditions, and core fantasy for a ZIL adventure before any coding begins

packaging

Prepare final adventure package with COVER, TAGLINE, SYNOPSIS, REVIEWS, METADATA artifacts and verify definition-of-done criteria