## 1. Separate desired behavior from constraints

Read source-data.json. List goal, allowed snippets, unchanged monthly price and unknowns. Deliver task-scope.md only. Do not inspect unrelated repositories or launch an agent.

Expected: A clear change boundary.
Check: Real repository and commands remain unknown.

## 2. Build before/after acceptance examples

Calculate old/new annual prices. Compare monthly, discount, annual amount and FAQ. Keep currency and rounding assumptions; use only the synthetic plan and infer no other tiers.

Expected: A price/copy acceptance table.
Check: Old1020, new 960 and monthly 100 can be independently checked.

## 3. Write a concrete implementation brief

Write implementation-brief.md: inspect real config/components, update discount and FAQ, explain 960, keep monthly unchanged, require actual screenshots and one-shot checks. Obtain commands from repository instructions; report missing commands. Add no dependencies or unrelated refactors.

Expected: A reviewable implementation task.
Check: Each requirement has a check; payment systems and other plans are out of scope.

## 4. Verify execution behavior and retain a local path

Compare local/cloud prerequisites: account, repository, starting state, cost and push/PR behavior. Current constraints forbid push and subagents, so provide a local plan only. Do not start an agent, branch or remote task.

Expected: A constraint-compliant execution plan.
Check: No unverified cloud setting is called a guarantee.

## 5. Check actual behavior after implementation

If later authorized for real local implementation, read project instructions and record the starting state. Modify only the confirmed scope. Check price, FAQ and mobile layout; report actual commands/results and real screenshots. Do not push, open a PR, deploy or delegate.

Expected: Local changes with evidence, or a blocker.
Check: Display and calculation agree; plans/mockups are not called completed work.

## 6. Deliver a reviewable result and clean temporary processes

Summarize files, price comparison, one-shot results, actual preview URL and unknowns. Clean unnecessary processes started for this task without stopping preexisting services. Leave changes unpushed, unmerged and undeployed.

Expected: A complete handoff.
Check: Changes and evidence are reviewable with no unnecessary background process.