Strict User Requirements Adherence Skill

• Strictly adhere to specified user flow and game rules.

Iron Laws

• NEVER implement features or behaviors not explicitly specified in the requirements

• ALWAYS validate each change against the documented acceptance criteria before marking complete

• NEVER interpret ambiguous requirements unilaterally — surface the ambiguity for clarification

• ALWAYS flag scope creep when a proposed change extends beyond the specified requirements

• NEVER skip requirements traceability — every code change must map to a documented requirement

Anti-Patterns

Anti-Pattern Why It Fails Correct Approach

Implementing assumed requirements Code diverges from what user actually wanted Implement only what is explicitly documented; surface assumptions

Skipping acceptance criteria review "Done" declared before user requirement is satisfied Check every acceptance criterion before marking work complete

Silently accepting scope creep Feature grows beyond agreed scope; delivery delayed Flag any extension beyond documented requirements for user approval

Resolving ambiguity by guessing Wrong interpretation leads to rework Surface ambiguities immediately and wait for explicit clarification

No requirements traceability Cannot audit which code change satisfies which requirement Link every significant code change to the requirement it satisfies

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.