story-acceptance_skill

Overview

This skill verifies and closes project stories after both frontend and backend tasks are completed. It prevents premature story closure by ensuring all related task files are checked and story acceptance criteria checkboxes are updated from - [ ] to - [x]. Use it to produce a clear readiness decision and to update the story file when appropriate.

How this skill works

Identify the story ID and load the story file from docs/reference/pm/stories/{story-id}.md. Find related task files by reading the story's "Related Tasks" section (preferred) or by pattern-matching task filenames in docs/reference/frontend/tasks/ and docs/reference/backend/tasks/. Read each task's > \*\*Status\*\*: field and confirm statuses are all completed before changing acceptance criteria checkboxes.

When to use it

• When frontend or backend notifies "task completed, please verify"
• When a user asks to "verify story", "accept story", "close story", or "mark story done"
• To determine if a story can be marked complete
• When asked "is story X done?" or "can we close story X?"
• Before merging or releasing features that depend on the story being closed

Best practices

• Always check BOTH docs/reference/frontend/tasks/ and docs/reference/backend/tasks/ for related tasks
• Prefer reading the story's "Related Tasks" list; fall back to filename pattern matching only if missing
• Treat any status other than completed as blocking (e.g., in\_progress or pending)
• If not all tasks are completed, list incomplete tasks and do NOT update checkboxes
• Update acceptance criteria exactly from - [ ] to - [x] only when all checks pass

Example use cases

• A frontend developer marks a task completed and asks QA to verify the story is ready to close
• A PM asks "is S-123 done?" and needs a definitive checklist and decision
• Automated verification step before changing a story's acceptance criteria in the repo
• A reviewer confirms both backend and frontend tasks finished before approving a release