Skip to content

nWave-ai/nWave / nWave/skills/nw-ab-validate-spec

nw-ab-validate-spec

Verified

PROCEDURE — validate an EXISTING agent spec against the nw-ab-validation-checklist. Trigger: checking a spec for compliance (also the shared composition target create/migrate/merge invoke). One job: run the checklist, report pass/fail.

nw-ab-validate-spec (PROCEDURE)

Kind: PROCEDURE | One job: validate an agent spec | One trigger: an existing agent spec must be checked for compliance (standalone, or composed by create/migrate/merge after a write).

This is the SHARED composition target. nw-ab-create-agent, nw-ab-migrate-monolith, and nw-ab-merge-agents all invoke this skill after writing — never re-inline the checklist.

Deterministic step-sequence (run every time, in order)

Run these steps in order:

  1. Checklist — run every item defined in nw-ab-validation-checklist, in table order, against the spec. Gate: each defined item reported pass/fail with evidence (line, count or quote); no item is claimed beyond those the checklist defines.

  2. Anti-patterns — run the anti-pattern scan (nw-ab-anti-patterns). Gate: zero anti-patterns.

Composition

  • COMPOSES (KNOWLEDGE): nw-ab-validation-checklist (the item definitions), nw-ab-anti-patterns, nw-ab-critique-dimensions, nw-agent-testing.
  • Note: the validator script scripts/validation/validate_framework_templates.py checks frontmatter, identity and declared-skill references. Reviewer artifact ownership is a role obligation, not a ban on native messaging tools.

Success Criteria

  • Every checklist item run in order
  • Anti-pattern scan run
  • Pass/fail reported per item
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall