Loading...
Loading...
Found 14 Skills
(NS) Spec-driven delivery face — clarify, requirements, tasks (including unit/e2e test tasks), implement, resume or continue a version from disk artifacts. Entry priority 2: feature specs, version work, multi-day scope, or "continue" / "resume version" when partial artifacts exist under docs/versions/. Auto-sizes and runs internal phases via references/. Prefer ns-coder for bare quick fixes. Do NOT use for brownfield onboarding, architecture rules, or /ns-harness prepare (manual only; never auto-run Prepare).
Goose-native software delivery command suite for product validation, scope challenge, planning, TDD implementation, debugging, review, QA, and release handoff
Post-task merge readiness gate with a state-backed explanation report and human explainability quiz
JFrog integration. Manage data, records, and automate workflows. Use when the user wants to interact with JFrog data.
Guides secure software delivery and DevSecOps for cleared/classified or high-side programs—disconnected or air-gapped CI/CD, artifact promotion across classification boundaries (conceptual), SBOM/signing/ provenance, SAST/DAST/secrets/IaC/container gates, supply-chain controls, STIG/CIS deploy baselines, IaC for classified landing zones, cleared developer workstations, build/deploy audit logging, and ATO/RMF pipeline evidence (not SSP ownership). Use for classified DevSecOps, cleared pipeline, high-side CI/CD, air-gapped build, cross-domain release, classified software delivery, STIG pipeline, ATO evidence CI, SBOM classified, secure software factory—not portfolio cyber governance (classified-cyber-security-senior-manager), ISSO/SSP (information-systems-security-officer-classified-specialist), commercial-only DevSecOps (devsecops), general DevOps (devops), build-only validation (build-validator), pentest (penetration-tester), or enterprise GRC-only (compliance-specialist).
DORA (DevOps Research and Assessment) Core Model for measuring and improving software delivery performance. Use this skill to assess team performance tier, identify capability gaps, and connect delivery metrics to product release strategy.
Acts as the sole DevFlow Planner only when explicitly invoked by the user or precisely routed after entry preparation is complete; responsible for requirements, repository takeover, Spec, Task DAG, global state, coordination, and merging; does not write production code, and is not used for explanation, general advice, or mere documentation editing.
Take a task and run it alone while the user is away, up to staged changes, an open PR or a merged PR. Stops on low confidence, growing blast radius or a block. Use when the user runs /afk with a task or issue.
Use this skill to run BMad (Breakthrough Method of Agile AI-Driven Development) as a harness-agnostic control-plane protocol that turns human intent into bounded, inspectable, resumable agent work. Compress intent into a five-field contract (Why, Capabilities, Constraints, Non-goals, Success signal); classify work as direct/bounded/initiative and route to the smallest safe path; carry decisions in durable artifacts; review as triage; route failure to the layer where ambiguity entered; and gate autonomy on observable acceptance with machine-readable status (draft/ready-for-dev/in-progress/in-review/done/blocked). Use when a change request, feature, delegated build, or multi-agent epic needs intent capture, bounded implementation, review, and resumability in any agent harness. Do not use for validating whether a problem is real (product-discovery), shaping bets before planning (product-shaping), formal spec/gate pipelines (spec-driven-development), or the issue-to-PR delivery flow (neckbeard).
Build an effort by orchestrating sub-agents, and deliver a pull request. Use when asked to build or orchestrate an effort from its spec and tickets.
Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort whose destination is unclear is routed to /ask-navigator before this pipeline starts). Humans own the checkpoints where there is no unique answer or the error cost is severe; agents continuously run everything repeatable and acceptable-by-evidence.
Implement an agreed change from findings, a spec, tickets or a concrete request; verify the result, prepare a draft PR and update authorized working records. Use when implementation is authorized, not for discovery or assessment alone.