The spec was built to be driven by Claude Code, Codex, Cursor or Gemini. You say what you want; the agent does the research, the edits and the checks; you decide what ships.
Why it works with agents
Agents are good at files and commands, and that is all the spec is: YAML and markdown in the repo, and a CLI that answers in JSON. There is no dashboard to drive, no session to keep. The agent works on the listing the way it works on your code.
Install the skills
A skill is a short guide the agent reads when the task calls for it. Install them once per repo:
$ npx skills add appeeky/skills
appeeky-specSet up the spec, find gaps, edit the listing, check and pushappeeky-spec-targetsPersonas, keyword research, which searches to targetappeeky-spec-localizeA new language or country, spare keyword spaceappeeky-spec-reviewDay-7 and day-14 results, keep or revert, the playbookappeeky-spec-cofounderThe weekly review: one listing change, a brief and a pull requestappeeky-spec-reviewsReview themes with counts, replies within each store's limitappeeky-spec-competitorsFinding competitors, what to do when one movesappeeky-spec-screenshotsApp Store screenshot sets, sizes, counts and testsappeeky-spec-socialPosts as files for every platform, comments and repliesappeeky-spec-ugcCreator personas, video briefs, the cost firstappeeky-spec-adsApple Search Ads, Meta and TikTok, paid searches worth targetingappeeky-spec-attributionWhere installs and revenue come from, smart links, data pullappeeky-spec-experimentsAny experiment's metric and result, pricing testsappeeky-spec-visibilityAI assistants naming the app, the category chartappeeky-spec-seoThe website: seo check, llms.txt, Search Console, Google ranksappeeky-spec-automationGitHub workflows and secrets, other CI, failed runsappeeky-spec-serverA VM or container host: Docker, the .env, logs, updates
Ask in plain words
“Get us ranking for “fan sounds” in the US.”
coverage → finds room in es-MX → edits → check
“Launch in Germany.”
targets for de → writes de-DE → check → diff
“Did last week's change work?”
verify → reads the verdict → proposes keep or revert
“Answer the one-star reviews.”
reviews list → drafts replies → leaves them for your review
What it does, and what it leaves to you
On its own
- Reads the playbook and past releases
- Researches searches and competitors
- Edits listing files and drafts replies
- Runs check, coverage, diff, verify
- Explains the change and opens a PR
Only when you say so
pushto the storespush --yes, skipping the questionreviews push, sending repliespullover files you edited
Everything has --json
Every command takes --json and prints the same facts as structured data, so an agent reads results instead of guessing from text. You can use it too, in scripts or your own tools.
$ npx @appeeky/spec coverage --country us --json$ npx @appeeky/spec diff --json$ npx @appeeky/spec verify --playbook --json
Review like code
The safest setup is the one you already have: the agent works on a branch and opens a pull request, the GitHub Action comments what will change, a person approves, and the merge ships it. See How it works with GitHub Actions.