[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C84AXD1C3R4W5J4ED84YN6":3,"skill-same:01M7C84AXD1C3R4W5J4ED84YN6":54},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7C84AXD1C3R4W5J4ED84YN6","grow-app",null,"Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs\u002F folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says 'users sign up then disappear'. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.","sung1-labs\u002Fsddx","sung1-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F325716214?v=4","01M7C7MDYAWVBFW42T3YCQYG7N","SunG1 Labs","01M7C7MDYZYBYQ5FNSK0XN0YY2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fai-skills\u002Fsddx-ai-grow-app\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: grow-app\ndescription: 'Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs\u002F folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says ''users sign up then disappear''. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.'\nlicense: MIT\nmetadata:\n  author: wondelai\n  version: \"1.0.2\"\n---\n\n# Grow an App\n\nYour app has users who sign up and then quietly disappear — cohorts decay, daily actives are flat, the activation funnel leaks where it always has, and nothing looks obviously broken. This journey seals the bucket: it turns first-time users into activated, then habitual, then would-miss-it users across eight interactive phases. The agent asks before every decision and records the outcome in `docs\u002F`, so the work resumes across sessions instead of restarting. Growth here is an engineering and design problem, not a bigger ad budget.\n\n## Core Principle\n\n**Fix the leaky bucket before pouring in acquisition: habit, activation, and retention come before any growth spend.** This skill sequences the eight phases, asks every decision question, and records each choice in `docs\u002F`. The constituent skills carry the method — invoke them rather than improvising their frameworks.\n\n## Journey Map\n\n| Phase | Skill | Question it answers | Artifact |\n|---|---|---|---|\n| 1 | hooked-ux | Why do users come back without us paying? | Extends docs\u002FPRODUCT.md |\n| 2 | improve-retention | Why don't new users reach the loop? | Extends docs\u002FPRODUCT.md |\n| 3 | continuous-discovery | What do our own users actually need? | Extends docs\u002FPRODUCT.md + docs\u002FCUSTOMER.md |\n| 4 | lean-ux | Which bet is worth building? | Extends docs\u002FEXPERIMENTS.md |\n| 5 | inspired-product | Is the team building the right things? | Extends docs\u002FPRODUCT.md |\n| 6 | lean-analytics | Which single number tells the truth? | Creates docs\u002FMETRICS.md — sets the Rule 8 bar |\n| 7 | microinteractions | Does it feel alive in the hand? | Extends docs\u002FDESIGN.md |\n| 8 | drive-motivation | Will engagement last, or curdle? | Extends docs\u002FPRODUCT.md |\n\nPhases 1-2 seal the loop and the funnel; 3-5 steer with evidence; 6 is the instrument panel; 7-8 are the finish and the ethical backstop. Take the lean-analytics baseline (Phase 6) early — before the Phase 1-2 fixes land — so every change is read against a pre-change number, then keep updating it. Habit formation is slow: read Phase 1's success against the \"5% rule\" (a habit has formed when 5%+ of users return unprompted), not a single cohort.\n\n## Operating Rules\n\n1. **Resume first.** Before anything else, read `docs\u002FGROW-APP-PLAN.md` and every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted.\n2. **Intake on first run only.** No tracker: run the Intake below, then create `docs\u002FGROW-APP-PLAN.md` with every phase statused `pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason`. Done when the tracker exists and the user has confirmed the phase plan.\n3. **Phase entry.** Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed \u002F skip \u002F defer — phases marked GATE may be deferred, never skipped. Mark the phase `in-progress` on proceed. Done when the user chose.\n4. **Skill invocation and fallback.** Load the phase's skill and use it: each phase's Invoke line names the skill by slug — use that skill to run the phase. If it is not available, offer: `npx skills add wondelai\u002Fskills\u002F\u003Cslug> --global`. If the user declines, run the phase from its Brief — the minimum viable method. State which mode you are in.\n5. **In-phase decisions.** Ask every question under \"Decide with the user\" — with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.\n6. **Phase exit.** Present the draft artifact content for sign-off before writing. On approval: write or extend the docs\u002F files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows `done`.\n7. **Artifact discipline.** Read before writing; create a file only if missing, otherwise extend — add or update your sections, preserve everyone else's. Files are UPPERCASE in `docs\u002F`. Every recommendation lands as a checkbox or a table row with owner and priority. See [references\u002Fartifact-templates.md](references\u002Fartifact-templates.md) when creating a docs\u002F file for the first time — create it from the full skeleton (all section headings), then fill the sections your phase names.\n8. **Retention before acquisition.** Acquisition-oriented phases — the optional cold-start-problem, contagious, and crossing-the-chasm, plus any paid-growth work — stay locked while activation and retention sit below the bar set at intake; unlock them only once the cohort curve clears that bar. Every habit loop and reward must pass the Manipulation Matrix: build only what the maker would use and honestly believes materially improves users. When a tactic needs manufactured anxiety or loss aversion, replace it with one built on real value.\n\n## Intake\n\nRun only on first start (no tracker). Ask:\n\n1. What does the app do, and what core action does a retained user repeat? (defines the Hook loop and the OMTM)\n2. What are the current retention numbers — day-1\u002F7\u002F30 or week-4 cohorts? (sets the Rule 8 acquisition bar; feeds lean-analytics)\n3. Where does the activation funnel leak, and what is the first-run flow? (gates improve-retention)\n4. Solo\u002Fsmall team or a full product trio (PM, designer, engineer)? (scales continuous-discovery and inspired-product)\n5. Is the app a network\u002Fmarketplace product, and do engaged users fail to convert to revenue? (flags optional cold-start-problem \u002F monetizing-innovation)\n6. What analytics and instrumentation exist today? (gates lean-analytics and every experiment)\n7. Is retention broken by UX or performance rather than missing engagement? (if yes, route to improve-app first)\n\nSkip heuristics: skip Phase 5 for a solo founder with no team to realign; defer Phase 7 until the loop and activation clear their bars; run Phase 3's cadence degraded if no user access exists yet. Then create the tracker from references\u002Fartifact-templates.md with every phase statused, and confirm the plan.\n\nDone when `docs\u002FGROW-APP-PLAN.md` exists with every phase statused and the user has confirmed the plan.\n\n## Phases\n\n### Phase 1 — Design the habit loop that brings users back (hooked-ux)\n\n**Purpose:** Build the engine of return — a Hook loop strong enough that users come back on an internal trigger, not a paid notification.\n\n**Brief (fallback):** The Hook Model runs Trigger → Action → Variable Reward → Investment. Migrate external triggers (push, email) to internal ones (an emotion — boredom, FOMO, anxiety). Make the action trivially simple. Make the reward variable across tribe\u002Fhunt\u002Fself. Sequence investment *after* the reward so it raises switching cost and loads the next trigger. A loop with one weak phase stalls, not half-works.\n\n**Invoke:** Use the `hooked-ux` skill with the core loop and how daily-active users return today. Ask it to (a) map the loop across all four phases, rate each 0-10, and name the weakest, and (b) design honest variable-reward concepts powered by data you already have, each checked against the Manipulation Matrix.\n\n**Decide with the user:**\n- Which internal trigger (emotion) should pull users back — confirm one.\n- Which single phase is weakest and gets the highest-leverage fix now — or defer if the loop is already forming (5%+ unprompted return).\n- Which reward type to strengthen — tribe (social), hunt (resources), or self (mastery) — rejecting any concept that fails the Manipulation Matrix.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Hook Model` (trigger → action → variable reward → investment; weakest phase named). Update the tracker.\n\n**Done when:** PRODUCT.md names the internal trigger and all four phases, the weakest phase and its fix are recorded, onboarding is re-engineered so a new user completes one full Hook cycle in the first session, and the user picked the fix to ship.\n\n### Phase 2 — Fix activation by making the first action almost effortless (improve-retention)\n\n**Purpose:** Get new users to the loop by making the first meaningful action almost effortless.\n\n**Brief (fallback):** B=MAP — behavior fires only when Motivation, Ability, and a Prompt converge. Motivation is unreliable; raise Ability instead. Simplicity is capped by the *scarcest* of six resources: time, money, physical effort, mental effort, social deviance, non-routineness. Shrink the target to a Starter Step that delivers value in under 30s, anchor it to an existing routine, and celebrate the win immediately.\n\n**Invoke:** Use the `improve-retention` skill with the real activation flow step by step and the day-1\u002F7\u002F30 drop-offs. Ask for a B=MAP friction audit rating all six Ability-Chain factors, the scarcest resource named, a Starter Step redesign, and event-based prompt rules.\n\n**Decide with the user:**\n- Which is the scarcest Ability resource for the first action — fix that link first, not the obvious one.\n- The Starter Step (tiniest valuable action) and its celebration moment.\n- Which time-based prompts convert to event-based, dropping any that fail \"would I appreciate this now?\".\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Activation & Retention Plan` (friction\u002Fmoment | fix | owner | status). Update the tracker.\n\n**Done when:** the scarcest resource is named, the Starter Step, celebration, and prompt changes are rows with owners, each day-1\u002F7\u002F30 drop-off is mapped to its likely B=MAP failure, and the user approved the fix list.\n\n### Phase 3 — Run continuous discovery so you stop guessing (continuous-discovery)\n\n**Purpose:** Replace generic best-practice with a weekly stream of evidence about your own users.\n\n**Brief (fallback):** Aim for at least one customer touchpoint per week. Build an Opportunity Solution Tree: outcome at the top → customer opportunities (needs\u002Fpains in the customer's words) → candidate solutions\u002Fexperiments. Never leap outcome→solution. Interviews are story-based (\"tell me about the last time you…\"), captured as one-page snapshots. Test the riskiest leap-of-faith assumption first, cheaply.\n\n**Invoke:** Use the `continuous-discovery` skill with the retention outcome and known churn patterns. Ask for an Opportunity Solution Tree, a current-state experience map of how churned users try to succeed today, a weekly story-based interview snapshot template, and an assumption map for the next planned feature.\n\n**Decide with the user:**\n- The single outcome at the top of the tree.\n- Which two or three opportunities to pursue first.\n- The weekly cadence and recruitment mechanism the team can actually sustain — set it now or run degraded.\n- The riskiest leap-of-faith assumption inside the next feature (desirability, viability, feasibility, usability) and the cheapest test for it.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Opportunity Solution Tree Notes`, `## Outcome Roadmap` (outcome\u002Fproblem | job served | priority | status), and `## Discovery Cadence`; extend docs\u002FCUSTOMER.md `## Interview Evidence` (date | who | facts | commitment). Update the tracker.\n\n**Done when:** the tree's outcome and top opportunities are recorded, the cadence is scheduled, the first interview snapshot template exists, and the riskiest assumption has a cheap test designed.\n\n### Phase 4 — Replace debate with cheap experiments (lean-ux)\n\n**Purpose:** Turn opportunities into falsifiable bets settled by behavior, not meetings.\n\n**Brief (fallback):** Outcomes over outputs — value is the behavior change, not the deliverable. Write a hypothesis: \"We believe [outcome] will happen if [persona] achieves [action] with [feature],\" with the metric and threshold committed *before* the test. Match fidelity to risk (a paper prototype with five users finds ~85% of usability issues); reserve A\u002FB tests for tuning a proven concept. When invalidated, remove from the backlog — don't defer.\n\n**Invoke:** Use the `lean-ux` skill with the biggest current design debate or a top discovery opportunity. Ask for three hypothesis statements in the standard format, the lowest-fidelity experiment that could validate the top one, and its pre-committed metric, threshold, and timebox.\n\n**Decide with the user:**\n- Which hypothesis to test first.\n- The experiment fidelity — the lowest that answers the actual question.\n- The pass\u002Ffail line and what leaves the backlog if it fails.\n\n**Artifact:** Extend docs\u002FEXPERIMENTS.md `## Experiment Cards` (hypothesis, type, primary metric + threshold, guardrail, decision rule) and `## Experiment Backlog` (idea | ICE | status). Update the tracker.\n\n**Done when:** at least one experiment card has a pre-committed threshold and decision rule, the backlog is triaged, and the user chose the first test.\n\n### Phase 5 — Build the right things with an empowered team (inspired-product)\n\n**Purpose:** Move the team from feature factory to outcome ownership — problems to solve, not features to ship.\n\n**Brief (fallback):** Empowered teams get problems, not backlogs, and answer for outcomes. Dual-track: discovery (what's worth building — addressing value, usability, feasibility, viability) runs continuously alongside delivery. Expect 10-20 discovery iterations per shipped feature. Give the team a product vision and an outcome-based roadmap so it can decide autonomously.\n\n**Invoke:** Use the `inspired-product` skill with the top three backlog requests and the current roadmap. Ask for an opportunity assessment of each (objective, target user, problem, success measure, alternatives) and a one-paragraph vision plus a quarter of outcome-based roadmap items.\n\n**Decide with the user:**\n- Which backlog request has the strongest evidence — and which to kill before it reaches a sprint.\n- The one-paragraph product vision.\n- Whether the roadmap is reframed as problems + key results rather than dated features.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Vision` and `## Outcome Roadmap` (outcome\u002Fproblem | job served | priority | status). Update the tracker.\n\n**Done when:** the vision paragraph exists, each of the three requests has a build\u002Fkill verdict, and the roadmap rows are outcomes, not features.\n\n### Phase 6 — Measure the one number that actually matters (lean-analytics)\n\n**Purpose:** Point the whole team at the One Metric That Matters and expose the vanity metrics hiding the decay.\n\n**Brief (fallback):** A good metric is comparative, a ratio\u002Frate (not a cumulative total), and behavior-changing. Business model dictates which metrics matter; stage dictates sequencing (Empathy → Stickiness → Virality → Revenue → Scale). Weak retention = Stickiness stage, so retention is the OMTM — working a later stage first is the canonical mistake. Draw a line in the sand (target, date, miss response), pair the OMTM with a counter-metric, and cohort the data.\n\n**Invoke:** Use the `lean-analytics` skill with the current dashboard\u002Fmetrics and the business model. Ask it to flag vanity metrics, pick the Stickiness-stage OMTM plus a counter-metric, design a one-screen dashboard (OMTM big, ≤6 supporting), and a cohorted retention view.\n\n**Decide with the user:**\n- The OMTM and its counter-metric.\n- The line in the sand — target, date, pre-committed miss response.\n- Which current metrics are retired as vanity.\n\n**Artifact:** Create docs\u002FMETRICS.md with `## Stage & One Metric That Matters`, `## KPI Definitions`, `## Baselines & Targets`, `## Funnel`, and `## Cohort Notes`. Update the tracker.\n\n**Done when:** METRICS.md names the OMTM + counter-metric, records the line in the sand with a date, lists cohorted baselines, the vanity metrics are marked retired, the one-screen dashboard is specified, and the retention bar for the Rule 8 acquisition gate is set.\n\n### Phase 7 — Polish the micro-moments that make it feel alive (microinteractions)\n\n**Purpose:** Close the gap between an app people tolerate and one they love, in the moments they touch daily.\n\n**Brief (fallback):** Every microinteraction has Trigger → Rules → Feedback → Loops & Modes. Feedback is immediate (\u003C100ms for direct manipulation) and proportionate; animate the element the user touched over a separate toast. Map every state: empty, loading, partial, error, disabled, double-tap. Invest in one or two signature moments that pass the removal test; use long loops to retire hints for power users.\n\n**Invoke:** Use the `microinteractions` skill with the five most-used interactions. Ask for a Trigger\u002FRules\u002FFeedback\u002FLoops audit of each, the sub-100ms feedback and missing edge-case states, and one signature moment implemented in real code.\n\n**Decide with the user:**\n- Which five interactions to audit.\n- Which one becomes the signature moment (removal test applied).\n- Which edge-case states to implement first.\n\n**Artifact:** Extend docs\u002FDESIGN.md `## Microinteraction Inventory` (interaction | trigger\u002Frules\u002Ffeedback\u002Floops | fix | status). Update the tracker.\n\n**Done when:** the five interactions are in the inventory with their missing states and fixes, the signature moment is chosen, and each fix has a status.\n\n### Phase 8 — Sustain engagement with intrinsic motivation (drive-motivation)\n\n**Purpose:** Keep the loops from curdling — engagement that runs on Autonomy, Mastery, and Purpose instead of exploitation.\n\n**Brief (fallback):** For any task needing cognitive effort, \"if-then\" rewards crush intrinsic motivation. Lasting engagement is Autonomy (choice over what\u002Fwhen\u002Fhow\u002Fwith whom), Mastery (visible progress, flow-calibrated challenge), and Purpose (why it matters). Autonomy killers: forced tutorials, unskippable steps, mandatory notifications. Reserve rewards for meaningful milestones; prefer \"now-that\" recognition over \"if-then\" bargains.\n\n**Invoke:** Use the `drive-motivation` skill with the app's gamification, streaks, points, and notification patterns. Ask for an AMP audit rated 0-10, every autonomy violation flagged, the point at which streaks tipped into loss aversion, and a progression redesign around real mastery and purpose.\n\n**Decide with the user:**\n- Which autonomy violations to remove (forced\u002Funskippable steps).\n- Which \"if-then\" rewards convert to \"now-that\" recognition.\n- Whether any streak\u002Fpoints mechanic exploits loss aversion and must change.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Activation & Retention Plan` with AMP-audit rows (violation\u002Ffinding | fix | owner | status). Update the tracker.\n\n**Done when:** the AMP score and every autonomy violation are recorded, the reward\u002Fstreak fixes are rows with owners, and the loops pass the Manipulation Matrix from Rule 8.\n\n## Optional Phases\n\n| Skill | Add when | Artifact |\n|---|---|---|\n| cold-start-problem | the app is a network or marketplace product | Extends docs\u002FPRODUCT.md |\n| monetizing-innovation | engaged users do not translate into revenue | Extends docs\u002FOFFER.md |\n| contagious | users love the app but never mention it | Extends docs\u002FMARKETING.md |\n| crossing-the-chasm | growth stalls at the early-adopter boundary | Extends docs\u002FSTRATEGY.md |\n| jobs-to-be-done | usage patterns say the app is hired for a different job | Extends docs\u002FCUSTOMER.md |\n\nOptional phases follow the same operating rules — load and use each listed skill exactly as a core phase would; insert where the Add-when condition first becomes true. The acquisition-leaning ones — cold-start-problem, contagious, crossing-the-chasm — stay locked behind Rule 8 until retention clears the bar.\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---|---|\n| Buying growth before fixing retention | Pass the Stickiness gate (a flattening cohort curve) before any acquisition spend; keep acquisition phases locked per Rule 8. |\n| Relying on external triggers forever | Migrate to an internal trigger via hooked-ux; treat notifications as scaffolding, not the load-bearing wall. |\n| Optimizing the wrong Ability-Chain link | Rate all six factors in improve-retention and fix the scarcest resource, not the most obvious one. |\n| Jumping from outcome straight to solution | Build the Opportunity Solution Tree in continuous-discovery first; the obvious feature is often the worst of five. |\n| Measuring outputs, not outcomes | Instrument every release; in lean-ux and inspired-product, success is a change in user behavior, not stories shipped. |\n| Gamifying with points for everything | Reserve rewards for meaningful milestones and run the drive-motivation AMP audit; \"if-then\" rewards crowd out your power users. |\n\n## Completing the Journey\n\n- [ ] PRODUCT.md holds a Hook loop with the weakest phase fixed, an activation Starter Step, a living Opportunity Solution Tree, and an AMP-clean engagement design.\n- [ ] METRICS.md names the Stickiness-stage OMTM plus a counter-metric with a line in the sand (target, date, miss response).\n- [ ] At least one lean-ux experiment has resolved with a recorded verdict, and invalidated ideas are out of the backlog.\n- [ ] The retention bar set at intake is met — or the remaining gap is quantified — before any acquisition phase runs.\n\nClose the tracker: every phase `done` or `skipped`, with Next Actions carried into PRODUCT.md, METRICS.md, and EXPERIMENTS.md. Then route forward:\n\n- When engagement mechanics cannot fix a product held back by broken UX or performance, continue with the `improve-app` skill.\n- When the app is sticking and the business around it must keep pace — revenue, channels, operations — continue with the `grow-business` skill.\n","# Grow an App\n\nYour app has users who sign up and then quietly disappear — cohorts decay, daily actives are flat, the activation funnel leaks where it always has, and nothing looks obviously broken. This journey seals the bucket: it turns first-time users into activated, then habitual, then would-miss-it users across eight interactive phases. The agent asks before every decision and records the outcome in `docs\u002F`, so the work resumes across sessions instead of restarting. Growth here is an engineering and design problem, not a bigger ad budget.\n\n## Core Principle\n\n**Fix the leaky bucket before pouring in acquisition: habit, activation, and retention come before any growth spend.** This skill sequences the eight phases, asks every decision question, and records each choice in `docs\u002F`. The constituent skills carry the method — invoke them rather than improvising their frameworks.\n\n## Journey Map\n\n| Phase | Skill | Question it answers | Artifact |\n|---|---|---|---|\n| 1 | hooked-ux | Why do users come back without us paying? | Extends docs\u002FPRODUCT.md |\n| 2 | improve-retention | Why don't new users reach the loop? | Extends docs\u002FPRODUCT.md |\n| 3 | continuous-discovery | What do our own users actually need? | Extends docs\u002FPRODUCT.md + docs\u002FCUSTOMER.md |\n| 4 | lean-ux | Which bet is worth building? | Extends docs\u002FEXPERIMENTS.md |\n| 5 | inspired-product | Is the team building the right things? | Extends docs\u002FPRODUCT.md |\n| 6 | lean-analytics | Which single number tells the truth? | Creates docs\u002FMETRICS.md — sets the Rule 8 bar |\n| 7 | microinteractions | Does it feel alive in the hand? | Extends docs\u002FDESIGN.md |\n| 8 | drive-motivation | Will engagement last, or curdle? | Extends docs\u002FPRODUCT.md |\n\nPhases 1-2 seal the loop and the funnel; 3-5 steer with evidence; 6 is the instrument panel; 7-8 are the finish and the ethical backstop. Take the lean-analytics baseline (Phase 6) early — before the Phase 1-2 fixes land — so every change is read against a pre-change number, then keep updating it. Habit formation is slow: read Phase 1's success against the \"5% rule\" (a habit has formed when 5%+ of users return unprompted), not a single cohort.\n\n## Operating Rules\n\n1. **Resume first.** Before anything else, read `docs\u002FGROW-APP-PLAN.md` and every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted.\n2. **Intake on first run only.** No tracker: run the Intake below, then create `docs\u002FGROW-APP-PLAN.md` with every phase statused `pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason`. Done when the tracker exists and the user has confirmed the phase plan.\n3. **Phase entry.** Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed \u002F skip \u002F defer — phases marked GATE may be deferred, never skipped. Mark the phase `in-progress` on proceed. Done when the user chose.\n4. **Skill invocation and fallback.** Load the phase's skill and use it: each phase's Invoke line names the skill by slug — use that skill to run the phase. If it is not available, offer: `npx skills add wondelai\u002Fskills\u002F\u003Cslug> --global`. If the user declines, run the phase from its Brief — the minimum viable method. State which mode you are in.\n5. **In-phase decisions.** Ask every question under \"Decide with the user\" — with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.\n6. **Phase exit.** Present the draft artifact content for sign-off before writing. On approval: write or extend the docs\u002F files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows `done`.\n7. **Artifact discipline.** Read before writing; create a file only if missing, otherwise extend — add or update your sections, preserve everyone else's. Files are UPPERCASE in `docs\u002F`. Every recommendation lands as a checkbox or a table row with owner and priority. See [references\u002Fartifact-templates.md](references\u002Fartifact-templates.md) when creating a docs\u002F file for the first time — create it from the full skeleton (all section headings), then fill the sections your phase names.\n8. **Retention before acquisition.** Acquisition-oriented phases — the optional cold-start-problem, contagious, and crossing-the-chasm, plus any paid-growth work — stay locked while activation and retention sit below the bar set at intake; unlock them only once the cohort curve clears that bar. Every habit loop and reward must pass the Manipulation Matrix: build only what the maker would use and honestly believes materially improves users. When a tactic needs manufactured anxiety or loss aversion, replace it with one built on real value.\n\n## Intake\n\nRun only on first start (no tracker). Ask:\n\n1. What does the app do, and what core action does a retained user repeat? (defines the Hook loop and the OMTM)\n2. What are the current retention numbers — day-1\u002F7\u002F30 or week-4 cohorts? (sets the Rule 8 acquisition bar; feeds lean-analytics)\n3. Where does the activation funnel leak, and what is the first-run flow? (gates improve-retention)\n4. Solo\u002Fsmall team or a full product trio (PM, designer, engineer)? (scales continuous-discovery and inspired-product)\n5. Is the app a network\u002Fmarketplace product, and do engaged users fail to convert to revenue? (flags optional cold-start-problem \u002F monetizing-innovation)\n6. What analytics and instrumentation exist today? (gates lean-analytics and every experiment)\n7. Is retention broken by UX or performance rather than missing engagement? (if yes, route to improve-app first)\n\nSkip heuristics: skip Phase 5 for a solo founder with no team to realign; defer Phase 7 until the loop and activation clear their bars; run Phase 3's cadence degraded if no user access exists yet. Then create the tracker from references\u002Fartifact-templates.md with every phase statused, and confirm the plan.\n\nDone when `docs\u002FGROW-APP-PLAN.md` exists with every phase statused and the user has confirmed the plan.\n\n## Phases\n\n### Phase 1 — Design the habit loop that brings users back (hooked-ux)\n\n**Purpose:** Build the engine of return — a Hook loop strong enough that users come back on an internal trigger, not a paid notification.\n\n**Brief (fallback):** The Hook Model runs Trigger → Action → Variable Reward → Investment. Migrate external triggers (push, email) to internal ones (an emotion — boredom, FOMO, anxiety). Make the action trivially simple. Make the reward variable across tribe\u002Fhunt\u002Fself. Sequence investment *after* the reward so it raises switching cost and loads the next trigger. A loop with one weak phase stalls, not half-works.\n\n**Invoke:** Use the `hooked-ux` skill with the core loop and how daily-active users return today. Ask it to (a) map the loop across all four phases, rate each 0-10, and name the weakest, and (b) design honest variable-reward concepts powered by data you already have, each checked against the Manipulation Matrix.\n\n**Decide with the user:**\n- Which internal trigger (emotion) should pull users back — confirm one.\n- Which single phase is weakest and gets the highest-leverage fix now — or defer if the loop is already forming (5%+ unprompted return).\n- Which reward type to strengthen — tribe (social), hunt (resources), or self (mastery) — rejecting any concept that fails the Manipulation Matrix.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Hook Model` (trigger → action → variable reward → investment; weakest phase named). Update the tracker.\n\n**Done when:** PRODUCT.md names the internal trigger and all four phases, the weakest phase and its fix are recorded, onboarding is re-engineered so a new user completes one full Hook cycle in the first session, and the user picked the fix to ship.\n\n### Phase 2 — Fix activation by making the first action almost effortless (improve-retention)\n\n**Purpose:** Get new users to the loop by making the first meaningful action almost effortless.\n\n**Brief (fallback):** B=MAP — behavior fires only when Motivation, Ability, and a Prompt converge. Motivation is unreliable; raise Ability instead. Simplicity is capped by the *scarcest* of six resources: time, money, physical effort, mental effort, social deviance, non-routineness. Shrink the target to a Starter Step that delivers value in under 30s, anchor it to an existing routine, and celebrate the win immediately.\n\n**Invoke:** Use the `improve-retention` skill with the real activation flow step by step and the day-1\u002F7\u002F30 drop-offs. Ask for a B=MAP friction audit rating all six Ability-Chain factors, the scarcest resource named, a Starter Step redesign, and event-based prompt rules.\n\n**Decide with the user:**\n- Which is the scarcest Ability resource for the first action — fix that link first, not the obvious one.\n- The Starter Step (tiniest valuable action) and its celebration moment.\n- Which time-based prompts convert to event-based, dropping any that fail \"would I appreciate this now?\".\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Activation & Retention Plan` (friction\u002Fmoment | fix | owner | status). Update the tracker.\n\n**Done when:** the scarcest resource is named, the Starter Step, celebration, and prompt changes are rows with owners, each day-1\u002F7\u002F30 drop-off is mapped to its likely B=MAP failure, and the user approved the fix list.\n\n### Phase 3 — Run continuous discovery so you stop guessing (continuous-discovery)\n\n**Purpose:** Replace generic best-practice with a weekly stream of evidence about your own users.\n\n**Brief (fallback):** Aim for at least one customer touchpoint per week. Build an Opportunity Solution Tree: outcome at the top → customer opportunities (needs\u002Fpains in the customer's words) → candidate solutions\u002Fexperiments. Never leap outcome→solution. Interviews are story-based (\"tell me about the last time you…\"), captured as one-page snapshots. Test the riskiest leap-of-faith assumption first, cheaply.\n\n**Invoke:** Use the `continuous-discovery` skill with the retention outcome and known churn patterns. Ask for an Opportunity Solution Tree, a current-state experience map of how churned users try to succeed today, a weekly story-based interview snapshot template, and an assumption map for the next planned feature.\n\n**Decide with the user:**\n- The single outcome at the top of the tree.\n- Which two or three opportunities to pursue first.\n- The weekly cadence and recruitment mechanism the team can actually sustain — set it now or run degraded.\n- The riskiest leap-of-faith assumption inside the next feature (desirability, viability, feasibility, usability) and the cheapest test for it.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Opportunity Solution Tree Notes`, `## Outcome Roadmap` (outcome\u002Fproblem | job served | priority | status), and `## Discovery Cadence`; extend docs\u002FCUSTOMER.md `## Interview Evidence` (date | who | facts | commitment). Update the tracker.\n\n**Done when:** the tree's outcome and top opportunities are recorded, the cadence is scheduled, the first interview snapshot template exists, and the riskiest assumption has a cheap test designed.\n\n### Phase 4 — Replace debate with cheap experiments (lean-ux)\n\n**Purpose:** Turn opportunities into falsifiable bets settled by behavior, not meetings.\n\n**Brief (fallback):** Outcomes over outputs — value is the behavior change, not the deliverable. Write a hypothesis: \"We believe [outcome] will happen if [persona] achieves [action] with [feature],\" with the metric and threshold committed *before* the test. Match fidelity to risk (a paper prototype with five users finds ~85% of usability issues); reserve A\u002FB tests for tuning a proven concept. When invalidated, remove from the backlog — don't defer.\n\n**Invoke:** Use the `lean-ux` skill with the biggest current design debate or a top discovery opportunity. Ask for three hypothesis statements in the standard format, the lowest-fidelity experiment that could validate the top one, and its pre-committed metric, threshold, and timebox.\n\n**Decide with the user:**\n- Which hypothesis to test first.\n- The experiment fidelity — the lowest that answers the actual question.\n- The pass\u002Ffail line and what leaves the backlog if it fails.\n\n**Artifact:** Extend docs\u002FEXPERIMENTS.md `## Experiment Cards` (hypothesis, type, primary metric + threshold, guardrail, decision rule) and `## Experiment Backlog` (idea | ICE | status). Update the tracker.\n\n**Done when:** at least one experiment card has a pre-committed threshold and decision rule, the backlog is triaged, and the user chose the first test.\n\n### Phase 5 — Build the right things with an empowered team (inspired-product)\n\n**Purpose:** Move the team from feature factory to outcome ownership — problems to solve, not features to ship.\n\n**Brief (fallback):** Empowered teams get problems, not backlogs, and answer for outcomes. Dual-track: discovery (what's worth building — addressing value, usability, feasibility, viability) runs continuously alongside delivery. Expect 10-20 discovery iterations per shipped feature. Give the team a product vision and an outcome-based roadmap so it can decide autonomously.\n\n**Invoke:** Use the `inspired-product` skill with the top three backlog requests and the current roadmap. Ask for an opportunity assessment of each (objective, target user, problem, success measure, alternatives) and a one-paragraph vision plus a quarter of outcome-based roadmap items.\n\n**Decide with the user:**\n- Which backlog request has the strongest evidence — and which to kill before it reaches a sprint.\n- The one-paragraph product vision.\n- Whether the roadmap is reframed as problems + key results rather than dated features.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Vision` and `## Outcome Roadmap` (outcome\u002Fproblem | job served | priority | status). Update the tracker.\n\n**Done when:** the vision paragraph exists, each of the three requests has a build\u002Fkill verdict, and the roadmap rows are outcomes, not features.\n\n### Phase 6 — Measure the one number that actually matters (lean-analytics)\n\n**Purpose:** Point the whole team at the One Metric That Matters and expose the vanity metrics hiding the decay.\n\n**Brief (fallback):** A good metric is comparative, a ratio\u002Frate (not a cumulative total), and behavior-changing. Business model dictates which metrics matter; stage dictates sequencing (Empathy → Stickiness → Virality → Revenue → Scale). Weak retention = Stickiness stage, so retention is the OMTM — working a later stage first is the canonical mistake. Draw a line in the sand (target, date, miss response), pair the OMTM with a counter-metric, and cohort the data.\n\n**Invoke:** Use the `lean-analytics` skill with the current dashboard\u002Fmetrics and the business model. Ask it to flag vanity metrics, pick the Stickiness-stage OMTM plus a counter-metric, design a one-screen dashboard (OMTM big, ≤6 supporting), and a cohorted retention view.\n\n**Decide with the user:**\n- The OMTM and its counter-metric.\n- The line in the sand — target, date, pre-committed miss response.\n- Which current metrics are retired as vanity.\n\n**Artifact:** Create docs\u002FMETRICS.md with `## Stage & One Metric That Matters`, `## KPI Definitions`, `## Baselines & Targets`, `## Funnel`, and `## Cohort Notes`. Update the tracker.\n\n**Done when:** METRICS.md names the OMTM + counter-metric, records the line in the sand with a date, lists cohorted baselines, the vanity metrics are marked retired, the one-screen dashboard is specified, and the retention bar for the Rule 8 acquisition gate is set.\n\n### Phase 7 — Polish the micro-moments that make it feel alive (microinteractions)\n\n**Purpose:** Close the gap between an app people tolerate and one they love, in the moments they touch daily.\n\n**Brief (fallback):** Every microinteraction has Trigger → Rules → Feedback → Loops & Modes. Feedback is immediate (\u003C100ms for direct manipulation) and proportionate; animate the element the user touched over a separate toast. Map every state: empty, loading, partial, error, disabled, double-tap. Invest in one or two signature moments that pass the removal test; use long loops to retire hints for power users.\n\n**Invoke:** Use the `microinteractions` skill with the five most-used interactions. Ask for a Trigger\u002FRules\u002FFeedback\u002FLoops audit of each, the sub-100ms feedback and missing edge-case states, and one signature moment implemented in real code.\n\n**Decide with the user:**\n- Which five interactions to audit.\n- Which one becomes the signature moment (removal test applied).\n- Which edge-case states to implement first.\n\n**Artifact:** Extend docs\u002FDESIGN.md `## Microinteraction Inventory` (interaction | trigger\u002Frules\u002Ffeedback\u002Floops | fix | status). Update the tracker.\n\n**Done when:** the five interactions are in the inventory with their missing states and fixes, the signature moment is chosen, and each fix has a status.\n\n### Phase 8 — Sustain engagement with intrinsic motivation (drive-motivation)\n\n**Purpose:** Keep the loops from curdling — engagement that runs on Autonomy, Mastery, and Purpose instead of exploitation.\n\n**Brief (fallback):** For any task needing cognitive effort, \"if-then\" rewards crush intrinsic motivation. Lasting engagement is Autonomy (choice over what\u002Fwhen\u002Fhow\u002Fwith whom), Mastery (visible progress, flow-calibrated challenge), and Purpose (why it matters). Autonomy killers: forced tutorials, unskippable steps, mandatory notifications. Reserve rewards for meaningful milestones; prefer \"now-that\" recognition over \"if-then\" bargains.\n\n**Invoke:** Use the `drive-motivation` skill with the app's gamification, streaks, points, and notification patterns. Ask for an AMP audit rated 0-10, every autonomy violation flagged, the point at which streaks tipped into loss aversion, and a progression redesign around real mastery and purpose.\n\n**Decide with the user:**\n- Which autonomy violations to remove (forced\u002Funskippable steps).\n- Which \"if-then\" rewards convert to \"now-that\" recognition.\n- Whether any streak\u002Fpoints mechanic exploits loss aversion and must change.\n\n**Artifact:** Extend docs\u002FPRODUCT.md `## Activation & Retention Plan` with AMP-audit rows (violation\u002Ffinding | fix | owner | status). Update the tracker.\n\n**Done when:** the AMP score and every autonomy violation are recorded, the reward\u002Fstreak fixes are rows with owners, and the loops pass the Manipulation Matrix from Rule 8.\n\n## Optional Phases\n\n| Skill | Add when | Artifact |\n|---|---|---|\n| cold-start-problem | the app is a network or marketplace product | Extends docs\u002FPRODUCT.md |\n| monetizing-innovation | engaged users do not translate into revenue | Extends docs\u002FOFFER.md |\n| contagious | users love the app but never mention it | Extends docs\u002FMARKETING.md |\n| crossing-the-chasm | growth stalls at the early-adopter boundary | Extends docs\u002FSTRATEGY.md |\n| jobs-to-be-done | usage patterns say the app is hired for a different job | Extends docs\u002FCUSTOMER.md |\n\nOptional phases follow the same operating rules — load and use each listed skill exactly as a core phase would; insert where the Add-when condition first becomes true. The acquisition-leaning ones — cold-start-problem, contagious, crossing-the-chasm — stay locked behind Rule 8 until retention clears the bar.\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---|---|\n| Buying growth before fixing retention | Pass the Stickiness gate (a flattening cohort curve) before any acquisition spend; keep acquisition phases locked per Rule 8. |\n| Relying on external triggers forever | Migrate to an internal trigger via hooked-ux; treat notifications as scaffolding, not the load-bearing wall. |\n| Optimizing the wrong Ability-Chain link | Rate all six factors in improve-retention and fix the scarcest resource, not the most obvious one. |\n| Jumping from outcome straight to solution | Build the Opportunity Solution Tree in continuous-discovery first; the obvious feature is often the worst of five. |\n| Measuring outputs, not outcomes | Instrument every release; in lean-ux and inspired-product, success is a change in user behavior, not stories shipped. |\n| Gamifying with points for everything | Reserve rewards for meaningful milestones and run the drive-motivation AMP audit; \"if-then\" rewards crowd out your power users. |\n\n## Completing the Journey\n\n- [ ] PRODUCT.md holds a Hook loop with the weakest phase fixed, an activation Starter Step, a living Opportunity Solution Tree, and an AMP-clean engagement design.\n- [ ] METRICS.md names the Stickiness-stage OMTM plus a counter-metric with a line in the sand (target, date, miss response).\n- [ ] At least one lean-ux experiment has resolved with a recorded verdict, and invalidated ideas are out of the backlog.\n- [ ] The retention bar set at intake is met — or the remaining gap is quantified — before any acquisition phase runs.\n\nClose the tracker: every phase `done` or `skipped`, with Next Actions carried into PRODUCT.md, METRICS.md, and EXPERIMENTS.md. Then route forward:\n\n- When engagement mechanics cannot fix a product held back by broken UX or performance, continue with the `improve-app` skill.\n- When the app is sticking and the business around it must keep pace — revenue, channels, operations — continue with the `grow-business` skill.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"wondelai","1.0.2","main","7d9c45c72ac89da53a28423808dabd6dc0be6795","skills\u002Flibrary\u002Fai-skills\u002Fsddx-ai-grow-app","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx","https:\u002F\u002Fgithub.com\u002Fsung1-labs","Building open-source tools for AI-assisted software development, spec-driven engineering, and reliable developer workflows.","2026-09-07 02:51:20",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add sung1-labs\u002Fsddx --skill grow-app",{"tool":40,"command":41},"bunx","bunx skills add sung1-labs\u002Fsddx --skill grow-app",{"tool":43,"command":44},"pnpm","pnpm dlx skills add sung1-labs\u002Fsddx --skill grow-app","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fai-skills\u002Fsddx-ai-grow-app\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fartifact-templates.md","REFERENCE","参考文档",2731,"https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fai-skills\u002Fsddx-ai-grow-app\u002Freferences\u002Fartifact-templates.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7C8TCN2HNT036445CS1VBHT","sddx-verify","Verify the complete SDDx change against its specifications, architecture, implementation, tests, security, operations, and deployment expectations.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-verify\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7C8T9FQKTSN971MP6RSV0GK","sddx-quick","Handle a small, bounded change with minimal durable artifacts while preserving verification and automatic escalation when scope grows.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-quick\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7C8T6C21FE8ZX8XDSJ5VJ5R","sddx-propose","Turn a resolved SDDx exploration into durable proposal, requirements, design, tasks, and optional RFC artifacts.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-propose\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7C8T2QDGTK9PPG4A3JXXS28","sddx-explore","Explore a change before implementation, resolve the applicable product, UX, architecture, security, testing, deployment, and operational questions, and recommend the next SDDx workflow.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-explore\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7C8SZ9GTETBRKEXT43EZ9G9","sddx-debug","Diagnose and fix a defect through reproduction, evidence-based hypotheses, a minimal fix, regression coverage, and verification.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-debug\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7C8SW14B7XG3TSQGGWZ0ZCH","sddx-archive","Complete a verified SDDx change, preserve its durable record, synchronize specifications, and recommend the next workflow.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-archive\u002FSKILL.md",[],[]]