What problem does it solve? When working on changes tracked by the Ether harness, writes that skip the mandatory phase order are hard-blocked by a PreToolUse hook. This Skill explains the required sequence (init, explore, proposal, spec/design, tasks, apply, verify, archive) so you know exactly which artifact or command is needed before writing code. ## Core Features & Use Cases - Phase Order Reference: Documents all eight stages and which artifact (proposal.md, spec.md, design.md, tasks.md, evidence.md, archive.md) completes each one. - TDD Gate Guidance: Explains that apply and verify fail closed if any file listed under the tasks.md ## Files section lacks a paired test or the test suite fails. - Violation Recovery: Describes how to read hook denial messages and write the missing artifact instead of working around the block. - Use Case: You attempt to edit source code and the hook denies the write because tasks.md does not exist yet; this Skill tells you to run ether status, write tasks.md with a ## Files section, then retry. ## Quick Start Ask the assistant to check the current Ether phase with ether status and explain which artifact must be written next before editing code.
