[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DM1QX8F3D95JSTEHC0P9QA":3,"skill-same:01M7DM1QX8F3D95JSTEHC0P9QA":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7DM1QX8F3D95JSTEHC0P9QA","next",null,"Decide the single next best thing to work on, with two alternates. Reads setup progress, work in progress, open PRs and failing CI, the backlog (GitHub Issues or Linear), overdue harness rituals, product decisions parked until now, and north-star analytics if PostHog is connected. Use when someone asks \"what next?\", \"what should I work on?\", at the start of a session, or after a PR merges.","foxinthehenhouse\u002Fapp-in-a-box","foxinthehenhouse","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F144333692?v=4","01M7DKXRK1CCGY9F45FYGWVD29","Kyle Fox","01M7DKXRKNG8A1ADJFXVH15RXT",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnext\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: next\ndescription: Decide the single next best thing to work on, with two alternates. Reads setup progress, work in progress, open PRs and failing CI, the backlog (GitHub Issues or Linear), overdue harness rituals, product decisions parked until now, and north-star analytics if PostHog is connected. Use when someone asks \"what next?\", \"what should I work on?\", at the start of a session, or after a PR merges.\n---\n\n# Next\n\nThe owner shouldn't need to know what to ask for. This skill looks at everything and\nproposes **one** action, plus two alternates, each with a one-line reason. It picks;\nit doesn't start. The owner says \"go\" (or picks an alternate), and then you run the\nskill it names.\n\n## 1. Gather signals (deterministic first)\n\n```bash\npython3 .agents\u002Fskills\u002Fnext\u002Fsignals.py --remote\n```\n\nThat returns JSON with setup progress, the current branch and work in progress, open\nPRs with failing checks, failing CI on `main`, open issues, overdue rituals, and\n`decisions_due`: product calls parked on day 0 in `design\u002Fbrief.json` → `decisions`\nwhose phase has now arrived (the first feature, pre-launch, post-launch), and\n`stale_flags`: feature flags past their `expires` date (`scripts\u002Fcheck_flags.py`). It also returns\n`risk_open`: the items the risk gate (`scripts\u002Frisk_gate.py`, the same check `ship` runs)\nsays are open, such as an unanswered risk question, an accepted risk with no owner or\ndate, or a screen that touches a category the idea was never screened for. If\n`gh_available` is false, say so in one line and carry on with local signals.\n\nThen add what the script can't read:\n- **Linear** (`tracker: linear` in `appbox.yaml`): Linear MCP `list_issues` for the\n  team, status Todo\u002FIn Progress, top 20 by priority.\n- **North star** (if the PostHog MCP is connected): the funnel of the 5 events in\n  `docs\u002Fproduct\u002FBRIEF.md` over the last 7 days. Note the step with the biggest\n  drop-off. If the MCP isn't connected, skip this and say \"analytics not read\".\n- **In-flight specs:** `ls docs\u002Fproduct\u002Fspecs\u002F` for any spec whose ticket has no\n  merged PR yet.\n\nIn Claude Code you may hand the CI-log and dependency reading to the `triage`\nsubagent (Haiku, cheap); in Codex, read them inline.\n\n## 2. Rank (first match wins the top slot)\n\n| Rank | Signal | Proposed action |\n|---|---|---|\n| 1 | Setup phase not done | Resume `new-app` at that phase |\n| 2 | `main` CI failing | Fix it: `backlog` to file a `fix` ticket, then fix on a branch |\n| 3 | Your open PR has failing checks or requested changes | `land` it: fixes CI and threads, then re-reviews |\n| 4 | Uncommitted or unpushed work on a feature branch | Finish it: gates, then PR |\n| 5 | Open PR with green CI, not yet reviewed | `land` it (runs `pr-review`, then merges or asks you) |\n| 6 | Ritual overdue by 2× its cadence | Run that ritual (`reflect`, `harness-optimize`, `north-star-report`, `market-watch`) |\n| 7 | Security or major dependency PR | `triage` it, then `pr-review` |\n| 8 | A `p0` ticket, or the ticket at the funnel's worst step | `feature-discovery` on it (or `build-feature` if it's specced) |\n| 9 | A risk item is open (`risk_open`) | Ask the open questions as one structured round and write each answer back to `design\u002Fbrief.json` → `risk`; a new category runs `python3 scripts\u002Frisk_gate.py rescreen` first. `ship` refuses until they're answered or accepted |\n| 10 | A decision is due (`decisions_due`) | Ask it as one structured question, the `docs\u002FDEFAULTS.md` answer recommended, and write the answer back to its ledger entry; `pre-launch` ones go to `ship` |\n| 10b | A flag is past its expiry (`stale_flags`) | Remove it (both registries and every `flag()`\u002F`useFlag()` call, then delete it in PostHog), or extend `expires` if its owner says it must stay: a `backlog` `chore` ticket, then a branch |\n| 11 | Next ticket by priority (`p0` > `p1` > `p2`, `ready` first) | `feature-discovery` \u002F `build-feature` |\n| 12 | Empty backlog | `north-star-report` to find the biggest drop-off, then file tickets |\n\nTie-break: the thing closest to users (a broken build beats a new feature), then the\ncheapest to finish. Never propose starting new work while one of your PRs is red.\n\n## 3. Answer (exactly this shape, under 12 lines)\n\nThe `Next:` line always names the skill in parentheses. An action without its skill\nleaves the owner asking \"how?\".\nExactly two alternates. Nothing goes after the `Signals read` line except the\nquestion: no \"after that…\" or \"also pending\" list, because a fourth option dilutes the pick.\n\n```\nNext: \u003Caction> (\u003Cskill to run>, e.g. `\u002Ffeature-discovery #14` or `$feature-discovery #14`)\nWhy: \u003Cthe signal, with its number: PR #, run, ticket, funnel step and %>\n\nOr:\n2. \u003Calternate>: \u003Cone-line why>\n3. \u003Calternate>: \u003Cone-line why>\n\nSignals read: setup ✓ · PRs ✓ · CI ✓ · backlog ✓ · rituals ✓ · decisions ✓ · flags ✓ · risk ✓ · analytics ✗ (PostHog not connected)\n```\n\nUse a structured question (`AskUserQuestion` in Claude Code, `request_user_input` in\nCodex) with the three options if the tool exists, otherwise ask in chat. On \"go\", run\nthe named skill. If you find a bug or scope while gathering signals, file it with\n`backlog` before answering. Don't keep a to-do list in chat.\n\n## Ask the owner\n\nFollow `.agents\u002Frules\u002Fproduct-judgement.md`: ask with a structured question (recommended option first), never decide these silently. In this skill that means: When two actions tie on rank, or the top one is a product call (a scope cut, launching, pricing), present the pick and alternates as one structured question instead of starting.\n","# Next\n\nThe owner shouldn't need to know what to ask for. This skill looks at everything and\nproposes **one** action, plus two alternates, each with a one-line reason. It picks;\nit doesn't start. The owner says \"go\" (or picks an alternate), and then you run the\nskill it names.\n\n## 1. Gather signals (deterministic first)\n\n```bash\npython3 .agents\u002Fskills\u002Fnext\u002Fsignals.py --remote\n```\n\nThat returns JSON with setup progress, the current branch and work in progress, open\nPRs with failing checks, failing CI on `main`, open issues, overdue rituals, and\n`decisions_due`: product calls parked on day 0 in `design\u002Fbrief.json` → `decisions`\nwhose phase has now arrived (the first feature, pre-launch, post-launch), and\n`stale_flags`: feature flags past their `expires` date (`scripts\u002Fcheck_flags.py`). It also returns\n`risk_open`: the items the risk gate (`scripts\u002Frisk_gate.py`, the same check `ship` runs)\nsays are open, such as an unanswered risk question, an accepted risk with no owner or\ndate, or a screen that touches a category the idea was never screened for. If\n`gh_available` is false, say so in one line and carry on with local signals.\n\nThen add what the script can't read:\n- **Linear** (`tracker: linear` in `appbox.yaml`): Linear MCP `list_issues` for the\n  team, status Todo\u002FIn Progress, top 20 by priority.\n- **North star** (if the PostHog MCP is connected): the funnel of the 5 events in\n  `docs\u002Fproduct\u002FBRIEF.md` over the last 7 days. Note the step with the biggest\n  drop-off. If the MCP isn't connected, skip this and say \"analytics not read\".\n- **In-flight specs:** `ls docs\u002Fproduct\u002Fspecs\u002F` for any spec whose ticket has no\n  merged PR yet.\n\nIn Claude Code you may hand the CI-log and dependency reading to the `triage`\nsubagent (Haiku, cheap); in Codex, read them inline.\n\n## 2. Rank (first match wins the top slot)\n\n| Rank | Signal | Proposed action |\n|---|---|---|\n| 1 | Setup phase not done | Resume `new-app` at that phase |\n| 2 | `main` CI failing | Fix it: `backlog` to file a `fix` ticket, then fix on a branch |\n| 3 | Your open PR has failing checks or requested changes | `land` it: fixes CI and threads, then re-reviews |\n| 4 | Uncommitted or unpushed work on a feature branch | Finish it: gates, then PR |\n| 5 | Open PR with green CI, not yet reviewed | `land` it (runs `pr-review`, then merges or asks you) |\n| 6 | Ritual overdue by 2× its cadence | Run that ritual (`reflect`, `harness-optimize`, `north-star-report`, `market-watch`) |\n| 7 | Security or major dependency PR | `triage` it, then `pr-review` |\n| 8 | A `p0` ticket, or the ticket at the funnel's worst step | `feature-discovery` on it (or `build-feature` if it's specced) |\n| 9 | A risk item is open (`risk_open`) | Ask the open questions as one structured round and write each answer back to `design\u002Fbrief.json` → `risk`; a new category runs `python3 scripts\u002Frisk_gate.py rescreen` first. `ship` refuses until they're answered or accepted |\n| 10 | A decision is due (`decisions_due`) | Ask it as one structured question, the `docs\u002FDEFAULTS.md` answer recommended, and write the answer back to its ledger entry; `pre-launch` ones go to `ship` |\n| 10b | A flag is past its expiry (`stale_flags`) | Remove it (both registries and every `flag()`\u002F`useFlag()` call, then delete it in PostHog), or extend `expires` if its owner says it must stay: a `backlog` `chore` ticket, then a branch |\n| 11 | Next ticket by priority (`p0` > `p1` > `p2`, `ready` first) | `feature-discovery` \u002F `build-feature` |\n| 12 | Empty backlog | `north-star-report` to find the biggest drop-off, then file tickets |\n\nTie-break: the thing closest to users (a broken build beats a new feature), then the\ncheapest to finish. Never propose starting new work while one of your PRs is red.\n\n## 3. Answer (exactly this shape, under 12 lines)\n\nThe `Next:` line always names the skill in parentheses. An action without its skill\nleaves the owner asking \"how?\".\nExactly two alternates. Nothing goes after the `Signals read` line except the\nquestion: no \"after that…\" or \"also pending\" list, because a fourth option dilutes the pick.\n\n```\nNext: \u003Caction> (\u003Cskill to run>, e.g. `\u002Ffeature-discovery #14` or `$feature-discovery #14`)\nWhy: \u003Cthe signal, with its number: PR #, run, ticket, funnel step and %>\n\nOr:\n2. \u003Calternate>: \u003Cone-line why>\n3. \u003Calternate>: \u003Cone-line why>\n\nSignals read: setup ✓ · PRs ✓ · CI ✓ · backlog ✓ · rituals ✓ · decisions ✓ · flags ✓ · risk ✓ · analytics ✗ (PostHog not connected)\n```\n\nUse a structured question (`AskUserQuestion` in Claude Code, `request_user_input` in\nCodex) with the three options if the tool exists, otherwise ask in chat. On \"go\", run\nthe named skill. If you find a bug or scope while gathering signals, file it with\n`backlog` before answering. Don't keep a to-do list in chat.\n\n## Ask the owner\n\nFollow `.agents\u002Frules\u002Fproduct-judgement.md`: ask with a structured question (recommended option first), never decide these silently. In this skill that means: When two actions tie on rank, or the top one is a product call (a scope cut, launching, pricing), present the pick and alternates as one structured question instead of starting.\n",{"name":5,"description":7},"main","82b5819f074e18b5d31db7a122e1f0ae5f5abbf7","plugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnext","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse","Not a developer","2026-10-06 17:24:46",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add foxinthehenhouse\u002Fapp-in-a-box --skill next",{"tool":37,"command":38},"bunx","bunx skills add foxinthehenhouse\u002Fapp-in-a-box --skill next",{"tool":40,"command":41},"pnpm","pnpm dlx skills add foxinthehenhouse\u002Fapp-in-a-box --skill next","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnext\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"signals.py","SCRIPT","脚本",10878,"https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnext\u002Fsignals.py",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DM2EPAFBTFNV5EW5GHKD5Q","ship","Release checklist for getting a build to testers or the stores. Runs the risk gate first (refuses while a risk item is open) and walks the owner through the compliance checklist. Covers the version bump, EAS build and submit, OTA updates and when they're safe, changelog, store listing, privacy nutrition label \u002F data safety form, the Accessibility Nutrition Labels, and the account-deletion requirement. Guidance-level; it never handles signing secrets. Use when asked to ship, release, submit to TestFlight \u002F App Store \u002F Play, or push an OTA update.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DM2AGRJ822B3C8NQCDK3JG","routines","Put the project's recurring rituals on a schedule, with the owner's consent. Weekly north-star report, monthly market watch, dependency triage, Supabase advisor sweep, reflect and harness-optimize. Uses Claude Code Routines (cloud cron) where they fit, and documents the Codex \u002F local cron equivalent. Use when asked to automate, schedule or \"keep the project moving on its own\", or after setup finishes.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Froutines\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DM27C3K1Y7FM0NZSBRSVEN","reflect","Consolidate what recent sessions learned into the project's long-term memory (.agents\u002Fmemory). Use at the end of a substantial session, after a correction from the user, after a painful debugging session, when the session-start healthcheck says reflect is overdue or a pending-reflection seed is waiting, or when MEMORY.md exceeds its budget.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Freflect\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DM2146TCNYXVVS2QXF08GS","pr-review","Review a pull request on the owner's behalf and fix what's safe to fix. Runs the deterministic gates first, then correctness\u002Fsecurity, design-system, accessibility and analytics review passes, verifies each blocking finding, applies safe fixes, re-checks, and ends with a plain-English verdict. Use when a PR is opened, when asked to review a PR, a branch or a pasted diff, or before merging anything.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fpr-review\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DM1X6QP3QAT47ET852S0P8","north-star-report","Weekly product-analytics and reliability readout. Pulls the funnel of the brief's 5 north-star events from PostHog, finds the biggest drop-offs and errors, checks each SLO in docs\u002Fslo.yaml against its error budget, compares with last week, and proposes (then, with a yes, files) tickets that target them. Use weekly, when the session-start line says it's overdue, when the backlog is empty, or when asked \"how is the app doing?\".","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnorth-star-report\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DM1NGHSRAY1NJVDWE1TG9Q","new-worktree","Create an isolated git worktree + branch off origin\u002Fmain for one unit of work, so parallel agents or sessions never share a checkout. Use when starting any ticket, or when another session may be working in the main checkout.","https:\u002F\u002Fgithub.com\u002Ffoxinthehenhouse\u002Fapp-in-a-box\u002Fblob\u002Fmain\u002Fplugins\u002Fapp-in-a-box\u002Ftemplate\u002F.agents\u002Fskills\u002Fnew-worktree\u002FSKILL.md",[],[]]