What problem does it solve? Cross-module HarmonyOS features and behavior changes often lose their agreed scope and acceptance criteria across sessions, reviews, and agent handoffs. This Skill establishes a single durable Markdown contract that records objectives, scope, non-goals, and acceptance scenarios so every session and reviewer verifies against the same success conditions. ## Core Features & Use Cases - Acceptance Contract Authoring: Creates one Markdown contract per feature at docs/feature-contracts/<slug>.md with Objective, Scope, Non-goals, Constraints, and evidence-based acceptance scenarios. - DSH-Native Integration: Reuses plan mode, todo_write, create_goal, subagents, and device tools instead of inventing a parallel process, with clear rules on when each mechanism applies. - Evidence-Driven Verification: Requires LSP checks after each source edit, code review against the contract, and UI or build evidence per scenario before marking the contract verified. - Cross-Session Continuity: Maintains an active-contract index in AGENTS.md so new sessions resume from the contract file rather than chat summaries. - Use Case: When adding a login feature spanning multiple ArkTS modules, create the contract, implement against it, capture s1-login.png evidence via UI verification, and mark the contract verified for later review. ## Quick Start Ask the agent to create an acceptance contract for the new HarmonyOS feature you are about to implement, including scope and acceptance scenarios.
