alamops-skills

Plugin alamops-skills from marketplace alamops-skills in alamops/skills. Commands read from the repo's manifest — 9 days ago.

Skills (15)

• appstore-review

  (alamops) Use whenever the user wants their iOS app checked against Apple's App Store Review Guidelines and submission requirements, or asks if Apple will reject something. Triggers — "will Apple reject this?", pre-submission audit, App Store readiness, pre-flight before TestFlight or App Store Conn

• appstore-seo

  (alamops) App Store Optimization (ASO) for the iOS App Store and Google Play — audit, write and rewrite store listings to rank and convert. Triggers — "/appstore-seo", app store SEO/ASO, "improve my app store ranking", "nobody finds my app", keyword research, writing app name / subtitle / keyword fi

• break-fix

  (alamops) Adversarial end-to-end bug hunt on a running app. Drives the real app like a hostile, confused, or impatient user — junk and boundary input, double-submits, out-of-order steps, back-button and refresh mid-flow, expired sessions, two tabs on one record, flaky network, tampered URL params —

• business-review

  (alamops) Analyzes a product/business from its public-facing materials (landing, pricing, onboarding, docs, app/UI, screenshots), separates real value from claimed value, generates 5–8 concrete buyer personas, ranks them across abundance / pain / urgency / WTP / retention / strategic leverage, recom

• code-review

  (alamops) Performs a thorough, read-only code review of any change source — a pull request, a git diff, uncommitted edits, recent commits, or code just produced in the conversation — and re-reviews a fix round, scoring each earlier finding fixed / partial / not fixed. Flags bugs; security and trust-

• create-tasks

  (alamops) Senior Technical PM that turns a PRD, brief, ticket, or conversation into a small set of deep, end-to-end dev/QA tasks. Performs mandatory deep repo-context analysis (entry points, data models, utilities, API patterns, sibling code paths) before drafting, asks one structured pass of clarif

• execute-plan

  (alamops) Executes only the coding work of an approved implementation plan, with parallel sub-agents that never collide. Cuts a branch and records the base SHA, checks no two tasks in a wave own the same file, gives each task's agent a self-contained brief with a no-TODO completeness clause, holds w

• grill

  (alamops) Hard, respectful interrogation of the owner about a feature or code change before it's planned or built, so no load-bearing unknown reaches the plan. Grounds itself in the code (or an `investigate` brief) first so it never asks what the repo answers, then presses in one or two structured p

• implement

  (alamops) The go-to skill for building and shipping a whole feature end to end — not just planning or reviewing one. Fire it on any `/implement` invocation — bare, with a task, with combinable modifier flags (`--auto` for unattended remote/CI runs, `--no-e2e`, `--no-spikes`, and `--no-follow-ups` to

• investigate

  (alamops) Grounded investigation of a feature or change before anyone plans or codes it. Fans out parallel read-only research agents over the codebase (entry points, sibling paths, test conventions, how the app runs), git history, and live library docs, then runs tiny scratchpad spikes to prove what

• rpg-persona

  (alamops) Runs a hard buyer-persona roleplay to pressure-test a sales pitch, message, or positioning. Impersonates a skeptical buyer (provided by the user, or chosen as the strongest skeptic from a prior business-review / personas doc) and forces the seller to earn every step — demanding numbers, pr

• test-loop

  (alamops) Runs a project's whole test suite — unit, integration and e2e — by itself, then drives it to green. Use it for any request to run the tests or the e2e suite, get a red suite or red CI green, or fix failing, broken or flaky tests (after a rebase or dependency bump), or to apply review must-

• to-prd

  (alamops) Drafts a Product Requirements Document (PRD) from any combination of inputs — a written description, the conversation, supporting media, a few provided files, linked docs/tickets, or a whole repository (either as enrichment or as the primary source when reverse-engineering existing code).

• write-plan

  (alamops) Writes a decomposition-ready implementation plan to `docs/plans/<slug>.md` — objective, grounded context with file:line anchors, approach and rejected alternatives, a work breakdown where each task owns files disjoint from its wave-siblings, test tasks by layer with an explicit e2e decisio

• write-tests

  (alamops) Writes the tests a change needs — unit, integration, and e2e whenever it has a user-visible flow or crosses a process boundary. Use it whenever the user asks for tests to be written, added or backfilled — for the changes on their branch vs main, a new endpoint, an under-tested module, or a

Similar plugins