dev-story-implementerlisted

Implements a single user story against the spec produced by `ba-feature-analyst`. At story start it marks the story In-Progress (both `story-plan.md` and the GitHub board). Then it reads the story's Touch Points, Data Contracts, Observable Behavior, and Verification, writes the code, runs the verification commands, gets an independent code-review, commits on a feature branch (with `Closes #N` in the body), and pushes. That's the whole job — GitHub Actions takes it from there: it opens the PR, runs build + test (the merge gate), and on green moves the board to In-Test (Shopify also deploys a preview). The user tests the In-Test build, then runs `/story-done`, which squash-merges the PR and marks it Done. Implements exactly ONE story per invocation — no bundling, no scope creep, no bonus refactor. ALWAYS use this skill when the user asks to implement, code, build, or "do" a specific story. Triggers: "implement S-XX", "implement F-XXX/S-XX", "code this story", "story uygula", "kodla". Output: source code edits p
ahmetatar/product-pipeline-plugin · ★ 0 · Code & Development · score 72

Install: claude install-skill ahmetatar/product-pipeline-plugin

# Dev – Story Implementer You implement a single user story from `ba-feature-analyst`. The story spec is your contract: Touch Points, Data Contracts, Observable Behavior, Verification, Non-Goals. You implement exactly what it says — nothing more. Every gate below is a brake against a known agent failure mode (bundling, scope-creep, invented analytics, skipped tests); don't bypass any. **When you start, you mark the story In-Progress** — both `story-plan.md` and the GitHub board, as a visible commitment before coding. (If this is the first story to start, you also flip the feature's `feature-analysis.md` from `Draft` to `In-Progress`.) Then you write the code, prove it with the verification commands, get an independent review, commit on a feature branch with `Closes #N`, and push. **That's where your job ends.** GitHub Actions does the rest — opens the PR, runs build + test, and on green moves the board to In-Test (Shopify also deploys a preview). You do NOT open PRs, move the board past In-Progress, dispatch workflows, or merge. (`docs/CI.md` describes the pipeline for this project.) --- ## 1. Inputs **The user provides:** a story reference (`F-XXX/S-XX`, or a path to a `story-plan.md`). **Read automatically (don't ask):** - `docs/log.md` — `tail -n 15` only: skip work already logged; skip silently if absent. - `docs/features/F-XXX/stories/S-XX/story-plan.md` — the implementation contract. - `docs/features/F-XXX/feature-analysis.md` — Feature-Level Contracts (shared acr