[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DDA0E6G6RMB8RFP6Y3EXM5":3,"skill-same:01M7DDA0E6G6RMB8RFP6Y3EXM5":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7DDA0E6G6RMB8RFP6Y3EXM5","init",null,"Onboard a Go repository to Atom: capture its initial baseline or confirm existing setup without changes. Keywords: init, onboard, setup, install atom, bootstrap, add atom to this repo.","girishmotwani\u002Fatom","girishmotwani","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20937791?v=4","01M7DD9G6RCNXB9G6A33Z0GA1P","01M7DD9G7VT0Z0JHV97PSR0GN9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: init\ndescription: 'Onboard a Go repository to Atom: capture its initial baseline or confirm existing setup without changes. Keywords: init, onboard, setup, install atom, bootstrap, add atom to this repo.'\n---\n\n# \u002Fatom:init\n\nSet up a Go repository, or confirm an existing matching setup without changes.\n\n## When to use\n\n- Adding Atom to a repository for the first time\n- Confirming that an already onboarded repository needs no changes\n- Diagnosing missing or corrupt onboarding without silently repairing it\n- Verifying the toolchain before starting a pipeline\n\n## Step 1 — Confirm this is a Go repository\n\nAtom is Go-scoped. It needs a `go.mod`.\n\nIf there isn't one, stop and ask the developer whether to create a module or whether\nAtom is the wrong tool here. Do not invent a module path.\n\n## Step 2 — Bootstrap the command\n\nCheck the **active session's** client identity against the supported minimum in\n[bootstrap.md](..\u002Fatom\u002Freferences\u002Fbootstrap.md), not the version of another\nexecutable. If it is unknown, conflicting or unsupported, ask one focused\nclarification or switch\u002Fupdate question and wait; do not update automatically.\nResolve Go's availability before invoking it. If missing, explain the prerequisite\nand ask the developer to supply it before continuing; do not install Go or run\nextra version\u002Fbuild checks instead of the baseline.\n\nFollow [bootstrap.md](..\u002Fatom\u002Freferences\u002Fbootstrap.md). It establishes working forms\nfor both `atom` and `atom-write-artifact` without replacing an installed package.\nRead it **before executing discovery commands**. Reuse forms already verified for\nthis session\u002Fenvironment; otherwise check availability before help or module calls.\nMissing tools are a setup decision: explain what is absent and ask before any\ninstallation. Healthy tools outside PATH are reused, not reinstalled. A found but\nbroken\u002Fpartial\u002Funsafe installation is preserved and reported, not silently repaired.\n\nGroup compatible read-only prerequisite checks into as few terminal invocations\nas safely possible, while following bootstrap's order and stop conditions. If a\ngroup cannot preserve a check's result or required decision, run it separately.\n\nKeep actual command statuses and relevant diagnostics; never truncate help\u002Fwriter\noutput with `head` or hide a failure behind a successful wrapper. A writer refusal\nor nonzero result stops the workflow, even if the wrapper reports zero. Do not probe\nan invalid writer target, continue with another write or bypass it with an editor.\nBootstrap approval does not approve later init or module-local artifact writes.\n\nOn Windows, keep working module forms when entry points are hidden; do not ask about\nchanging PATH during normal init. If the developer requests PATH setup, bootstrap\nprovides the one-time `setup-path` opt-in. After successful setup, use its printed\nabsolute executable commands in this session. Do not re-probe command names or ask\nagain to locate the same executables.\n\nDo not locate or read Atom's Python source while onboarding another repository.\nUse the command forms established by bootstrap from the target module directory;\nuse `--help` when an option is unclear, not the implementation in an external\ncheckout or installed package.\n\nExisting `.atom\u002F` files do not require an implementation audit. Read the named local\nfiles in steps 4 and 5 and report any discrepancy. If `atom init` refuses because\nexisting setup is conflicting, incomplete, or corrupt, preserve it and report the\nnamed problem; do not add `--force`\nwithout the developer's explicit approval to discard that state.\n\n## Step 3 — Run deterministic onboarding\n\n```bash\natom init\n```\n\nOn a valid matching repeat, this command returns 0 with an explicit **read-only no-op**\nmessage. It does not refresh the baseline, detect build commands again, reset approvals,\nupdate the local bundle, append events, or change files and timestamps.\n\nAn existing `.atom\u002F` with conflicting, incomplete, or corrupt setup returns a nonzero\nerror without repair. Restore or repair the named files before retrying. Explicit\n`--force` deliberately resets the project record and discards recorded approvals; it\nis not a workaround for a normal repeat.\n\nOn first initialization, this one command performs the operations that must agree:\n\n- runs the untouched no-race baseline before writing Atom files;\n- records the exact result in `.atom\u002Fbaseline.json`, including failures;\n- infers the module path and records the verified build\u002Ftest commands;\n- prefers the repository's own `make build` \u002F `make test` when a Makefile defines them;\n- creates the project scaffold and installs the local instruction bundle.\n\nOn first initialization it creates:\n\n```\n.atom\u002F\n  atom\u002F                  # self-contained local instructions and skills\n  config.json       # module path, build\u002Ftest commands, model roles, coverage target\n  state.json        # pipeline + phase state\n  events.jsonl      # structured event log\n  baseline.json     # the pre-Atom check result\nspecs\u002F              # pipeline artifacts\npoc\u002F                # throwaway spikes\n```\n\nIf the printed baseline is failing, tell the developer immediately. Do not repair the\nrepository during onboarding unless asked. A pre-existing failure discovered three\nphases later looks like something Atom caused.\n\nMaintains a marked block in `.gitignore` for machine-local runtime data:\n`.atom\u002Fbaseline.json`, `.atom\u002Fevents.jsonl`, and `.atom\u002Fevents.lock`. Existing ignore\nrules are preserved. `.atom\u002Fconfig.json`, `.atom\u002Fstate.json`, and `.atom\u002Fatom\u002F**`\nremain tracked because they are shared project configuration, approvals, and\ninstructions.\n\nIgnore rules do not untrack files already committed. If Git already tracks one of\nthese generated files, tell the developer to remove that specific path from the index\nwith `git rm --cached \u003Cpath>` after confirming it is safe; never run the command\nsilently or untrack the whole `.atom\u002F` directory.\n\n`specs\u002F` and `poc\u002F` are **committed** — they are the reviewable record of how the code\ncame to look the way it does.\n\n## Step 4 — Confirm the recorded commands\n\nFor first initialization, read `.atom\u002Fconfig.json` and confirm the module, build\ncommand, and test command match the baseline that `atom init` printed. Do not rewrite\nthe file through a generic edit tool; a mismatch is an onboarding defect to report.\n\nFor a successful no-op, report the preserved configuration. No new baseline was run,\nso do not compare commands to a newly printed baseline or claim they were reverified.\n\nA repository with a Makefile will show `make build` and `make test` rather than the Go\ndefaults, and `atom init` prints the reason it chose them. This is expected, not a\ndefect: the project's own build usually carries tags, ldflags or generation steps that\n`go build .\u002F...` would silently skip. Targets are resolved one at a time, so a Makefile\nwith only `build` correctly leaves the test command Go-native. If `make` is not\ninstalled, Atom says so and stays on the Go defaults rather than running a command that\ncannot work.\n\n## Step 5 — Confirm the local instructions\n\nOn first initialization, `atom init` copies instructions, references, templates and\nskills into `.atom\u002Fatom\u002F`. It also creates or updates\n`.github\u002Fcopilot-instructions.md` with a relative link to that local bundle.\nNothing in the target repository should point back to the Atom checkout or an\ninstalled-plugin directory.\n\nIf the repository already has Copilot instructions, `atom init` preserves them and\nadds the managed local reference once.\n\n### Keep verification approval-free\n\nAfter first initialization, verify onboarding by reading these named files:\n\n- `.atom\u002Fconfig.json`\n- `.atom\u002Fbaseline.json`\n- `.atom\u002Fatom\u002Fmanifest.json`\n- `.github\u002Fcopilot-instructions.md`\n- `.gitignore`\n\nAfter a successful no-op, the same shared-file reads are sufficient without\n`.atom\u002Fbaseline.json`: machine-local baseline and event files may be absent on a clone.\nDo not recreate them or require empty `specs\u002F` and `poc\u002F` directories to be restored.\nThe no-op validates shared onboarding structurally, not the installed bundle's version\nor every instruction's content.\n\nDo not run `git status`, recursive shell scans, or another Atom command on the normal\nsuccess path. The init output plus these file reads prove the contract without asking\nthe developer for more shell approvals. Run a follow-up command only when the init\noutput or one of these files exposes a specific discrepancy.\n\n## Step 6 — Report\n\nTell the developer:\n\n- For first initialization: the baseline result, including every failed gate, and\n  what was created\n- For a no-op: setup was already valid, nothing changed, and no baseline was refreshed\n- The two established command forms, once, for reuse in subsequent beats\n- The recommended model setup — see [model-guidance.md](..\u002Fatom\u002Freferences\u002Fmodel-guidance.md)\n- For first initialization: next step `\u002Fatom:discover`; for a no-op: resume the\n  existing workflow, using `\u002Fatom-status` if its position is unclear\n\nUse the appropriate skill available in the active client. If a documented alias is\nunknown or rejected, disclose that rather than guessing another alias or reinstalling\nthe plugin. Naming the intended skill in ordinary language does not prove a slash\nalias works; invoke that skill, not a silently substituted beat.\n\n---\n\n## Done when\n\n- [ ] `go.mod` confirmed\n- [ ] `atom init` completed\n- [ ] First init: no-race baseline captured before any Atom file was written\n- [ ] First init: `.atom\u002F`, `specs\u002F`, `poc\u002F` created; `.gitignore` updated\n- [ ] First init: config commands match the commands exercised by the baseline\n- [ ] Repeat: valid matching setup confirmed without changes or a new baseline\n- [ ] Local Atom bundle present under `.atom\u002Fatom\u002F`\n- [ ] Repository agent instructions reference the local bundle\n- [ ] Developer briefed, including model guidance\n\n## Next\n\nFirst initialization: `\u002Fatom:discover`. Successful no-op: resume the existing workflow.\n","# \u002Fatom:init\n\nSet up a Go repository, or confirm an existing matching setup without changes.\n\n## When to use\n\n- Adding Atom to a repository for the first time\n- Confirming that an already onboarded repository needs no changes\n- Diagnosing missing or corrupt onboarding without silently repairing it\n- Verifying the toolchain before starting a pipeline\n\n## Step 1 — Confirm this is a Go repository\n\nAtom is Go-scoped. It needs a `go.mod`.\n\nIf there isn't one, stop and ask the developer whether to create a module or whether\nAtom is the wrong tool here. Do not invent a module path.\n\n## Step 2 — Bootstrap the command\n\nCheck the **active session's** client identity against the supported minimum in\n[bootstrap.md](..\u002Fatom\u002Freferences\u002Fbootstrap.md), not the version of another\nexecutable. If it is unknown, conflicting or unsupported, ask one focused\nclarification or switch\u002Fupdate question and wait; do not update automatically.\nResolve Go's availability before invoking it. If missing, explain the prerequisite\nand ask the developer to supply it before continuing; do not install Go or run\nextra version\u002Fbuild checks instead of the baseline.\n\nFollow [bootstrap.md](..\u002Fatom\u002Freferences\u002Fbootstrap.md). It establishes working forms\nfor both `atom` and `atom-write-artifact` without replacing an installed package.\nRead it **before executing discovery commands**. Reuse forms already verified for\nthis session\u002Fenvironment; otherwise check availability before help or module calls.\nMissing tools are a setup decision: explain what is absent and ask before any\ninstallation. Healthy tools outside PATH are reused, not reinstalled. A found but\nbroken\u002Fpartial\u002Funsafe installation is preserved and reported, not silently repaired.\n\nGroup compatible read-only prerequisite checks into as few terminal invocations\nas safely possible, while following bootstrap's order and stop conditions. If a\ngroup cannot preserve a check's result or required decision, run it separately.\n\nKeep actual command statuses and relevant diagnostics; never truncate help\u002Fwriter\noutput with `head` or hide a failure behind a successful wrapper. A writer refusal\nor nonzero result stops the workflow, even if the wrapper reports zero. Do not probe\nan invalid writer target, continue with another write or bypass it with an editor.\nBootstrap approval does not approve later init or module-local artifact writes.\n\nOn Windows, keep working module forms when entry points are hidden; do not ask about\nchanging PATH during normal init. If the developer requests PATH setup, bootstrap\nprovides the one-time `setup-path` opt-in. After successful setup, use its printed\nabsolute executable commands in this session. Do not re-probe command names or ask\nagain to locate the same executables.\n\nDo not locate or read Atom's Python source while onboarding another repository.\nUse the command forms established by bootstrap from the target module directory;\nuse `--help` when an option is unclear, not the implementation in an external\ncheckout or installed package.\n\nExisting `.atom\u002F` files do not require an implementation audit. Read the named local\nfiles in steps 4 and 5 and report any discrepancy. If `atom init` refuses because\nexisting setup is conflicting, incomplete, or corrupt, preserve it and report the\nnamed problem; do not add `--force`\nwithout the developer's explicit approval to discard that state.\n\n## Step 3 — Run deterministic onboarding\n\n```bash\natom init\n```\n\nOn a valid matching repeat, this command returns 0 with an explicit **read-only no-op**\nmessage. It does not refresh the baseline, detect build commands again, reset approvals,\nupdate the local bundle, append events, or change files and timestamps.\n\nAn existing `.atom\u002F` with conflicting, incomplete, or corrupt setup returns a nonzero\nerror without repair. Restore or repair the named files before retrying. Explicit\n`--force` deliberately resets the project record and discards recorded approvals; it\nis not a workaround for a normal repeat.\n\nOn first initialization, this one command performs the operations that must agree:\n\n- runs the untouched no-race baseline before writing Atom files;\n- records the exact result in `.atom\u002Fbaseline.json`, including failures;\n- infers the module path and records the verified build\u002Ftest commands;\n- prefers the repository's own `make build` \u002F `make test` when a Makefile defines them;\n- creates the project scaffold and installs the local instruction bundle.\n\nOn first initialization it creates:\n\n```\n.atom\u002F\n  atom\u002F                  # self-contained local instructions and skills\n  config.json       # module path, build\u002Ftest commands, model roles, coverage target\n  state.json        # pipeline + phase state\n  events.jsonl      # structured event log\n  baseline.json     # the pre-Atom check result\nspecs\u002F              # pipeline artifacts\npoc\u002F                # throwaway spikes\n```\n\nIf the printed baseline is failing, tell the developer immediately. Do not repair the\nrepository during onboarding unless asked. A pre-existing failure discovered three\nphases later looks like something Atom caused.\n\nMaintains a marked block in `.gitignore` for machine-local runtime data:\n`.atom\u002Fbaseline.json`, `.atom\u002Fevents.jsonl`, and `.atom\u002Fevents.lock`. Existing ignore\nrules are preserved. `.atom\u002Fconfig.json`, `.atom\u002Fstate.json`, and `.atom\u002Fatom\u002F**`\nremain tracked because they are shared project configuration, approvals, and\ninstructions.\n\nIgnore rules do not untrack files already committed. If Git already tracks one of\nthese generated files, tell the developer to remove that specific path from the index\nwith `git rm --cached \u003Cpath>` after confirming it is safe; never run the command\nsilently or untrack the whole `.atom\u002F` directory.\n\n`specs\u002F` and `poc\u002F` are **committed** — they are the reviewable record of how the code\ncame to look the way it does.\n\n## Step 4 — Confirm the recorded commands\n\nFor first initialization, read `.atom\u002Fconfig.json` and confirm the module, build\ncommand, and test command match the baseline that `atom init` printed. Do not rewrite\nthe file through a generic edit tool; a mismatch is an onboarding defect to report.\n\nFor a successful no-op, report the preserved configuration. No new baseline was run,\nso do not compare commands to a newly printed baseline or claim they were reverified.\n\nA repository with a Makefile will show `make build` and `make test` rather than the Go\ndefaults, and `atom init` prints the reason it chose them. This is expected, not a\ndefect: the project's own build usually carries tags, ldflags or generation steps that\n`go build .\u002F...` would silently skip. Targets are resolved one at a time, so a Makefile\nwith only `build` correctly leaves the test command Go-native. If `make` is not\ninstalled, Atom says so and stays on the Go defaults rather than running a command that\ncannot work.\n\n## Step 5 — Confirm the local instructions\n\nOn first initialization, `atom init` copies instructions, references, templates and\nskills into `.atom\u002Fatom\u002F`. It also creates or updates\n`.github\u002Fcopilot-instructions.md` with a relative link to that local bundle.\nNothing in the target repository should point back to the Atom checkout or an\ninstalled-plugin directory.\n\nIf the repository already has Copilot instructions, `atom init` preserves them and\nadds the managed local reference once.\n\n### Keep verification approval-free\n\nAfter first initialization, verify onboarding by reading these named files:\n\n- `.atom\u002Fconfig.json`\n- `.atom\u002Fbaseline.json`\n- `.atom\u002Fatom\u002Fmanifest.json`\n- `.github\u002Fcopilot-instructions.md`\n- `.gitignore`\n\nAfter a successful no-op, the same shared-file reads are sufficient without\n`.atom\u002Fbaseline.json`: machine-local baseline and event files may be absent on a clone.\nDo not recreate them or require empty `specs\u002F` and `poc\u002F` directories to be restored.\nThe no-op validates shared onboarding structurally, not the installed bundle's version\nor every instruction's content.\n\nDo not run `git status`, recursive shell scans, or another Atom command on the normal\nsuccess path. The init output plus these file reads prove the contract without asking\nthe developer for more shell approvals. Run a follow-up command only when the init\noutput or one of these files exposes a specific discrepancy.\n\n## Step 6 — Report\n\nTell the developer:\n\n- For first initialization: the baseline result, including every failed gate, and\n  what was created\n- For a no-op: setup was already valid, nothing changed, and no baseline was refreshed\n- The two established command forms, once, for reuse in subsequent beats\n- The recommended model setup — see [model-guidance.md](..\u002Fatom\u002Freferences\u002Fmodel-guidance.md)\n- For first initialization: next step `\u002Fatom:discover`; for a no-op: resume the\n  existing workflow, using `\u002Fatom-status` if its position is unclear\n\nUse the appropriate skill available in the active client. If a documented alias is\nunknown or rejected, disclose that rather than guessing another alias or reinstalling\nthe plugin. Naming the intended skill in ordinary language does not prove a slash\nalias works; invoke that skill, not a silently substituted beat.\n\n---\n\n## Done when\n\n- [ ] `go.mod` confirmed\n- [ ] `atom init` completed\n- [ ] First init: no-race baseline captured before any Atom file was written\n- [ ] First init: `.atom\u002F`, `specs\u002F`, `poc\u002F` created; `.gitignore` updated\n- [ ] First init: config commands match the commands exercised by the baseline\n- [ ] Repeat: valid matching setup confirmed without changes or a new baseline\n- [ ] Local Atom bundle present under `.atom\u002Fatom\u002F`\n- [ ] Repository agent instructions reference the local bundle\n- [ ] Developer briefed, including model guidance\n\n## Next\n\nFirst initialization: `\u002Fatom:discover`. Successful no-op: resume the existing workflow.\n",{"name":5,"description":7},"main","5bb33cbe2c835382b5ccda840c5268321b24ac0b","skills\u002Finit","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom","https:\u002F\u002Fgithub.com\u002Fgirishmotwani","curious about all things distributed ","2026-11-13 16:16:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add girishmotwani\u002Fatom --skill init",{"tool":36,"command":37},"bunx","bunx skills add girishmotwani\u002Fatom --skill init",{"tool":39,"command":40},"pnpm","pnpm dlx skills add girishmotwani\u002Fatom --skill init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7DDBYEX4YKKBSQQP3HEGJC1","tdd","Implement one phase test-first in Go: red, green, refactor, against an approved design spec. Keywords: TDD, test driven, test first, implement, red green refactor, build the phase, write the code.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7DDBT5MMFRRBZJQ01VHNDGK","spec","Write the high-level design spec for one phase, grounded in that phase POC evidence. Keywords: spec, design, design doc, architecture, API design, describe the approach.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7DDBQ3NXQKG74B1RCHDKK9T","ship","Commit, push and open a pull request for a completed phase, with the pipeline artifacts linked. Keywords: ship, PR, pull request, commit, push, open a PR, submit.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7DDBJMHEDT9VPGR1GJZD8CN","review","Standalone or phase multi-model review of a Go diff, merged into one report with severities. Keywords: review, code review, multi-model review, review my changes, review the diff, critique.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7DDBD2G9WVYVFCTYNYFTWAE","poc","Build, run and evaluate a throwaway Go spike that answers one falsifiable question. Produces a POC Report with verbatim evidence. Keywords: POC, proof of concept, spike, prototype, prove it, experiment, try it out.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fpoc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7DDB98QNSK2WG5MMHH7S6J4","plan","Break proven work into ordered, independently shippable phases based on POC evidence. Keywords: plan, phases, break down, roadmap, decompose, milestones, sequencing.","https:\u002F\u002Fgithub.com\u002Fgirishmotwani\u002Fatom\u002Fblob\u002Fmain\u002Ftools\u002Fatom\u002Fassets\u002Fskills\u002Fplan\u002FSKILL.md",[],[]]