ahmetatar
UserClaude Code plugin that takes a product from idea to shipped, reviewed code — skills + subagents + per-stack CI/CD (iOS · Shopify · web SaaS)
Categories
Indexed Skills (8)
ba-feature-analyst
Acts as a Business Analyst (BA) to produce a complete, agent-ready feature analysis document and sequential per-story files for a single feature referenced from the product backlog. Output is optimized for downstream coding agents (Claude Code) — every story is self-contained, with explicit file targets, data contracts, and verification steps. ALWAYS use this skill when the user asks to analyze, break down, or detail a specific feature from the backlog. Triggers: "analyze this feature", "break down feature", "write user stories for", "story breakdown", "split into stories". Output: one feature summary file at docs/features/[F-XXX]-[feature-slug]/feature-analysis.md and one file per story at docs/features/[F-XXX]-[feature-slug]/stories/[S-XX]-[story-slug]/story-plan.md
dev-story-implementer
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
devops-ci-architect
Sets up GitHub Actions CI/CD for a project. Every stack gets the same standard pipeline: push a feat branch → a PR opens (auto-pr.yml) → CI runs build + test as the merge gate (ci.yml) → when CI is green the board moves to In-Test, and Shopify additionally deploys the app to the store (in-test.yml). (dev-story-implementer set the board to In-Progress at story start.) Stacks differ only in their build/test commands and their on-green deploy step. iOS also ships a manual TestFlight button. Stack-specific details live in templates/stacks/<id>/manifest.md — adding a project type is a drop-in directory, no skill-body edits. ALWAYS use this skill when the user asks to set up CI/CD, GitHub Actions, deploy/release automation, or a build pipeline. Triggers: "set up CI", "github actions kur", "ci/cd workflow", "release workflow", "shopify deploy", "ci kur". Output: .github/workflows/ (ci.yml + auto-pr.yml + in-test.yml + the stack's release/distribution workflow) + .github/scripts/set-project-status.sh + stack support
pd-design-foundation
Acts as a Product Designer to establish the app-wide design system before any UI or UX work begins. Produces two artifacts: a platform-neutral spec at `docs/design-system.md` AND a platform-specific tokens code file that downstream UI agents import directly. ALWAYS use this skill once per project, after the PO backlog is ready and before the first BA story is written. Must also be triggered if no `design-system.md` exists when UX or UI work is about to start. Triggers: "create design system", "design foundation", "design tokens", "set up design system", "no design system yet". Output: `docs/design-system.md` + a platform-specific tokens file. Runs ONCE per project; updates in place if `docs/design-system.md` already exists.
po-backlog
Acts as a Product Owner to generate a prioritized, agent-ready feature backlog from an existing market analysis report. Output is optimized for downstream consumers: the BA feature-analyst skill (per-feature breakdowns), the design-foundation skill (persona-driven aesthetics), and the po-product-intake skill (additive updates over time). Requires `docs/market_analysis_report.md`. Triggers: "generate feature backlog", "create backlog", "feature backlog", "backlog oluştur", "mvp roadmap". Output: `docs/feature_backlog.md`. Runs ONCE per project; updates in place if it already exists.
po-market-analyst
Acts as a Product Owner (PO) to perform deep App Store market analysis. Scoped explicitly to the App Store (iOS and/or Android). Output is shaped for consumption by the `po-backlog` skill: stable section IDs, category benchmarks, audience signals, feature × competitor matrix, and evidence-gated pain points. This skill does NOT generate the feature backlog — that is `po-backlog`'s job. ALWAYS use this skill when the user provides a keyword to search on the App Store or asks for competitor research. Triggers: "analyze app store category", "market analysis", "competitor research", "app store opportunity", "search app store for", "analyze keyword". Output: `docs/market_analysis_report.md` only.
po-product-intake
Acts as a Product Owner to capture, analyse, and add new ideas, features, improvements, or requests to an existing product backlog. Conversational by design — guides the user through intent → definition → backlog check → priority → confirmation → write. Output strictly matches the `po-backlog` schema so downstream agents (BA, designer) consume it without re-interpretation. ALWAYS use this skill when the user wants to add something new to the product — a brand-new feature, a UX improvement, a competitive response, a user complaint, or a rough idea to explore. Triggers: "yeni bir fikrim var", "şu özelliği ekleyelim", "I have an idea", "add this feature", "new feature request", "users are asking for". Output: updated `docs/feature_backlog.md` (matching po-backlog schema) + optional intake report at `docs/intake/[YYYY-MM-DD]-[feature-slug].md`.
system-architect
Acts as a Solution Architect to establish a project's TECHNICAL foundation exactly once, before any design or story work. Picks the project type + tech stack, scaffolds the real folder structure and toolchain (init, install dependencies), VERIFIES that build/test/lint commands actually run, and records everything in `CLAUDE.md` (a standardized `## Project Profile` block) and `docs/REFERENCES.md` (folder map + Verified Commands + conventions). Downstream skills (pd-design-foundation, ba-feature-analyst, dev-story-implementer, devops-ci-architect) read this foundation instead of re-deriving the stack. Runs AFTER po-backlog, BEFORE pd-design-foundation. ALWAYS use this skill to set up a new project's technical foundation, choose its stack, or scaffold its folder structure. Triggers: "set up the project", "scaffold the project", "establish tech stack", "choose the stack", "folder structure", "proje kur", "klasör yapısı", "stack belirle". Output: scaffolded project skeleton + `CLAUDE.md` `## Project Profile` block
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.