Menú
SkillsMP ha recopilado 47 skills de nobodyonlyc/harness-skills. Abre una skill para revisar su origen y sus detalles.
Mostrando 40 de 47 skills recopiladas.
Single entry point — classify ANY incoming prompt into a lifecycle route (build/change the product through the 9 phases) OR a direct route (one-off task dispatched straight to a skill), set mode, then dispatch. Nothing dead-ends. Use when: a new prompt…
Idioma del texto original: inglés
Phase 6 code review — inspect a child-task diff across correctness, security, contract, scope, and clarity, and record tracked findings to evidence
Idioma del texto original: inglés
Phase 8 QA loop — run the task's selected test set and drive a reproduce-fix-re-verify loop until everything is green, with a cap and escalation when it cannot converge. Use when: a coded+reviewed task needs its tests driven to green, the Phase 8 QA gate, a…
Idioma del texto original: inglés
Phase 6 review-fix loop — run an independent (adversarial) reviewer, track each finding as a checklist in evidence, then loop fix -> re-review until every finding is resolved. The review counterpart of check-qa. Use when: a child-task diff is coded and needs…
Idioma del texto original: inglés
Phase 6/7 deep security review — audit a change for auth, injection, secrets, data exposure, and dependency risk, recording tracked findings. Use when: the change touches authentication/authorization, secrets, sensitive/PII data, file uploads, an…
Idioma del texto original: inglés
Create a new project from a prompt — drive a greenfield idea through the full 9-phase lifecycle (BA, design, UI, plan, code, review, test, fixbug, deploy), step-gated and persona-aware. Use when: starting a greenfield project, an empty repo and the user asked…
Idioma del texto original: inglés
Fix a bug on an existing harness project via structured debugging — build a reliable pass/fail signal first, then hypothesize, confirm, and fix minimally. Use when: a reported bug, a hard-to-reproduce failure, a regression, a mysterious/intermittent error,…
Idioma del texto original: inglés
Execute one backlog User Story end-to-end on an existing harness project through the gated phase chain (BA delta, design, plan, code, review, test, verify, ship). Use when: executing a single backlog US, workflow-intake routed case 2/3, a per-US iteration…
Idioma del texto original: inglés
Coordinate solo vs team development on a shared harness backlog — claim, branch, per-assignee WIP=1, PR integration gate, handoff, and features.json conflict resolution. Use when: multiple people/agents share one backlog, deciding solo vs team mode,…
Idioma del texto original: inglés
Phase 2 API design — define endpoints/operations, request/response contracts, status/error model, and versioning between components. Use when: defining endpoints/operations, specifying request/response contracts, designing an error/status model, or setting a…
Idioma del texto original: inglés
Phase 2 system architecture — define components, boundaries, data flow, and stack, recording the choice as an ADR with a trade-off matrix plus a machine-readable Stack block. Always research the current latest LTS/stable versions before deciding; pin to them.…
Idioma del texto original: inglés
Phase 5 backend implementation — implement a child-task's server-side logic (services, persistence, endpoints) following the design docs and language conventions. Use when: implementing server-side logic for a child-task, building…
Idioma del texto original: inglés
Phase 5 CLI implementation — build command-line interfaces for a child-task with clear argument parsing, exit codes, and scriptable output. Use when: building a command-line interface for a child-task, defining commands/flags/exit codes, making output…
Idioma del texto original: inglés
Phase 5 database implementation — write migrations, schema objects, and data-access code for a child-task per the data design. Use when: writing a migration, implementing schema objects/indexes/constraints, building data-access code, or the Phase 5 database…
Idioma del texto original: inglés
Phase 5 frontend implementation — build the UI for a child-task from the approved mockups and UX flows, following component and language conventions. Use when: building UI for a child-task, implementing screens/components from approved mockups, wiring a…
Idioma del texto original: inglés
Phase 5 implementation in Go — language idioms, tooling, and project layout. Composes with a component skill (dev-be/dev-cli/dev-batch). Use when: the stack is Go, implementing a component skill in Go, or setting Go tooling (modules, go test) and layout.
Idioma del texto original: inglés
Phase 5 implementation in JavaScript/TypeScript (Node) — language idioms, tooling, and project layout. Composes with a component skill (dev-be/dev-fe/dev-cli). Use when: the stack is Node/JS/TS, implementing a component skill in JavaScript/TypeScript, or…
Idioma del texto original: inglés
Phase 5 implementation in Python — language idioms, tooling, and project layout. Composes with a component skill (dev-be/dev-cli/dev-batch). Use when: the stack is Python, implementing a component skill in Python, or setting Python tooling (venv, packaging)…
Idioma del texto original: inglés
Phase 5 implementation in Rust — language idioms, tooling, and project layout. Composes with a component skill (dev-be/dev-cli/dev-batch). Use when: the stack is Rust, implementing a component skill in Rust, or setting Rust tooling (cargo, clippy) and layout.
Idioma del texto original: inglés
Phase 7 end-to-end testing — drive complete user-facing flows through the real system to confirm it works as the user experiences it. For any UI, E2E code must cover the ENTIRE system — every user-facing flow from design-ux-flow gets a spec; no flow left…
Idioma del texto original: inglés
Phase 7 unit testing via test-driven tracer bullets — write one behavior test through the public interface, make it pass, repeat. Always required. Use when: writing new logic, adding a unit-level behavior, the test-strategy selects unit (always),…
Idioma del texto original: inglés
Phase 4 skeleton generation — create the minimal project/file structure and build tooling for a greenfield project so the dev phase has a working frame. Use when: scaffolding a greenfield project's structure and build tooling, or producing a runnable frame…
Idioma del texto original: inglés
Phase 2 stack version research — for every technology in the chosen stack, web-research the current latest LTS/stable from the official source and record it to docs/design/stack-versions.md (version + channel + source URL + as-of date). Use when: pinning…
Idioma del texto original: inglés
Phase 1 backlog generation — turn a requirements doc into prioritized User Stories with acceptance criteria and seed the harness backlog. Use when: turning requirements into a prioritized US backlog, writing User Stories with acceptance criteria, seeding the…
Idioma del texto original: inglés
Token optimization — activate the vendored caveman skill to compress inter-agent prompts and subagent results, cutting output tokens without weakening any quality gate. Use when: compressing inter-agent prompts or subagent results, a long-running run is…
Idioma del texto original: inglés
Phase 9 commit message — write a Conventional Commit message from the staged diff. Mechanical, fast-tier. Use when: writing a commit message, summarizing a staged diff, or producing a Conventional Commit line.
Idioma del texto original: inglés
Phase 7 test selector — decide which test types a task requires (unit always; integration, regression, e2e, performance, security conditionally) from its characteristics, and emit them as harness verifications. Use when: choosing test types for a child-task…
Idioma del texto original: inglés
Phase 7 integration testing — verify that components work together across real boundaries (DB, API, services) for tasks that cross components or call external dependencies. Every integration test must be a written test case with explicit steps, concrete…
Idioma del texto original: inglés
Phase 7 regression testing — re-run the broader test suite for the touched area to prove a change did not break existing behavior. Required whenever a task edits live code or data. Use when: a change edits/refactors live code, alters a DB schema or shared…
Idioma del texto original: inglés
Read-only exploration — locate code, files, and conventions across the codebase and return conclusions, not file dumps. Fast, single-agent. Use when: locating where something lives in the codebase, learning a convention before editing, or answering a…
Idioma del texto original: inglés
Phase 5 batch/job implementation — build scheduled or bulk-processing jobs for a child-task with idempotency, checkpointing, and observability. Use when: building a scheduled or bulk-processing job, needing idempotency/checkpointing/back-pressure, processing…
Idioma del texto original: inglés
Explain code, architecture, or a change to the user at the right level of detail for their role (plain for non-technical, precise for developers). Use when: explaining how code/architecture/a change works, onboarding someone to a subsystem, or answering "what…
Idioma del texto original: inglés
Mechanical file operations — create, move, rename, or delete files and directories. Fast-tier, low-judgment. Use when: creating/moving/renaming/deleting files or directories as a mechanical step, not as part of a larger judgment-heavy change.
Idioma del texto original: inglés
Make a small, scoped fix without the full feature pipeline — typos, one-line bugs, config tweaks — still tested and lightly reviewed. Use when: a typo/one-line bug/config tweak that doesn't warrant the full feature pipeline, but still needs a test + light…
Idioma del texto original: inglés
Phase 9 pull request — open a PR with a clear summary, the test evidence, and a review checklist; the entry to the team integration gate. Use when: opening a PR for a finished feature branch, entering the team integration gate, or packaging a change with its…
Idioma del texto original: inglés
Phase 9 deploy — release a build to an environment. Deploying to any non-local environment is an always-stop action requiring explicit user confirmation. Use when: deploying a build to any environment, releasing to staging/production, running deploy-time…
Idioma del texto original: inglés
Phase 9 release — cut a versioned release with a changelog and tag once features are verified. Strong-tier (judgment about version + scope). Use when: cutting a versioned release, choosing a semver bump, writing a changelog, or tagging/publishing verified…
Idioma del texto original: inglés
Phase 7 performance testing — measure latency/throughput/resource use against a stated NFR. Required only when the task has a performance requirement. Use when: a task states a latency/throughput NFR, measuring p95/throughput against a target, or the…
Idioma del texto original: inglés
Phase 7 security testing — check authentication/authorization, input handling, secrets, and known-vulnerability surface. Required when the task touches auth, secrets, sensitive data, or an external surface. Use when: a task touches auth/authz, handles secrets…
Idioma del texto original: inglés
Phase 4 task planning — split a User Story into vertical child-tasks and freeze the per-task test-strategy into the harness verifications before start (they are immutable afterwards). Use when: splitting a US into child-tasks, decomposing bootstrap Stage A,…
Idioma del texto original: inglés