alamops · Agent Skills
共 9 个 Skill,均有经来源核对的实质文档。打开卡片可阅读原始说明,了解包内文件和安装方式。
execute-plan
(alamops) Executes only the coding work of an approved implementation plan, with parallel sub-agents that never collide. Cuts a branch and records the base SHA, checks no two tasks in a wave own the same file, gives each task's agent a self-contained brief with a no-TODO completeness clause, holds wave barriers, isolates unavoidable shared files in worktrees, routes reported remainder into the next wave, and commits a checkpoint per wave. Use when the user hands over a plan (docs/plans/ .md, a w
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
grill
(alamops) Hard, respectful interrogation of the owner about a feature or code change before it's planned or built, so no load-bearing unknown reaches the plan. Grounds itself in the code (or an investigate brief) first so it never asks what the repo answers, then presses in one or two structured passes on scope, business rules, edge and error states, data and contract changes, migrations, budgets, rollout, the acceptance bar, and every remainder that would become a follow-up. Pushes back on vagu
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
implement
(alamops) The go-to skill for building and shipping a whole feature end to end — not just planning or reviewing one. Fire it on any /implement invocation — bare, with a task, with combinable modifier flags (--auto for unattended remote/CI runs, --no-e2e, --no-spikes, and --no-follow-ups to bar even owner-deferred remainder — also accepted as --no-followups, --nofollowups, --no-follow-up, --no-followup, --nofollowup), or as --config/--update — and whenever the user asks in plain words to actually
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
investigate
(alamops) Grounded investigation of a feature or change before anyone plans or codes it. Fans out parallel read-only research agents over the codebase (entry points, sibling paths, test conventions, how the app runs), git history, and live library docs, then runs tiny scratchpad spikes to prove what reading can't settle. Saves what we know / proved / assume / must ask, plus a completeness inventory of every caller, propagation point and existing-data surface, to docs/plans/ -investigation.md. Us
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
rpg-persona
(alamops) Runs a hard buyer-persona roleplay to pressure-test a sales pitch, message, or positioning. Impersonates a skeptical buyer (provided by the user, or chosen as the strongest skeptic from a prior business-review / personas doc) and forces the seller to earn every step — demanding numbers, proof, differentiation, and pricing logic. After every in-character reply, returns a coaching block covering what landed, what missed, which objection was triggered, hidden buying signals, and what to d
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
test-loop
(alamops) Runs a project's whole test suite — unit, integration and e2e — by itself, then drives it to green. Use it for any request to run the tests or the e2e suite, get a red suite or red CI green, or fix failing, broken or flaky tests (after a rebase or dependency bump), or to apply review must-fixes and re-run — even a plain "run the tests", and even when a database or other services must be brought up first. Owns the e2e lifecycle itself — starts services and the app, waits for real readin
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
to-prd
(alamops) Drafts a Product Requirements Document (PRD) from any combination of inputs — a written description, the conversation, supporting media, a few provided files, linked docs/tickets, or a whole repository (either as enrichment or as the primary source when reverse-engineering existing code). Acts as a senior CPO collaborator who surfaces unknowns as clarifying questions before writing, then produces a Markdown PRD covering problem, goals, personas, functional and non-functional requiremen
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
write-plan
(alamops) Writes a decomposition-ready implementation plan to docs/plans/ .md — objective, grounded context with file:line anchors, approach and rejected alternatives, a work breakdown where each task owns files disjoint from its wave-siblings, test tasks by layer with an explicit e2e decision and run recipe, execution waves, blast radius, open assumptions, and a completeness ledger dispositioning every would-be follow-up. Builds on investigate/grill output when present, else grounds itself read
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日
write-tests
(alamops) Writes the tests a change needs — unit, integration, and e2e whenever it has a user-visible flow or crosses a process boundary. Use it whenever the user asks for tests to be written, added or backfilled — for the changes on their branch vs main, a new endpoint, an under-tested module, or an e2e flow — in any framework (jest, vitest, pytest, Playwright, Cypress…). Works from a plan's test breakdown, a branch diff, or a named module or flow; fans out agents partitioned by module under te
- 1小时安装量
- 1
- GitHub Stars
- 53
- 最近更新
- 11月18日