51 skills — copy the install command to get started.
12 skills shown
sdd/general/init-sdd
Sets up a complete Spec-Driven Development (SDD) project structure — either as a new project directory or layered into an existing one — adapted to the user's language stack and coding agent. Trigger when the user invokes /init-sdd, says "set up SDD", "initialize SDD", or "add SDD to this project".
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/general/init-sddsdd/kairos-development/specforge
Use when a feature should be built from a spec — fresh, partially implemented, or complete — and you want sub-agents to execute the Spec Kit pipeline (specs/<feature>/) to production-ready code with human approval gates. Entry point for the specforge suite; also use to resume a stalled tasks.md or verify a finished one.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforgesdd/kairos-development/specforge-author
Use when a feature has no spec yet (specs/<feature>/ missing) or an incomplete Spec Kit artifact set (spec.md without plan.md or tasks.md) and the goal is a complete, human-approved spec/plan/tasks ready for specforge execution.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-authorsdd/kairos-development/specforge-cursor
Cursor-native Spec Kit orchestration hub — same gates, modes, lenses, and production bar as Claude's specforge, but dispatch uses Cursor Task agents and Cursor Orchestrate cloud workers. Use when the human is in Cursor CLI/IDE and wants to build from specs/<feature>/ (fresh, resume, validate, attended, autonomous, or zero-touch). Claude Code users must use specforge instead — do not substitute this skill on Claude.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-cursorsdd/kairos-development/specforge-cursor-author
Cursor-native Spec Kit authoring — drives a feature from nothing or a partial specs/<feature>/ tree to approved spec.md/plan.md/tasks.md, then hands off to specforge-cursor. Use on Cursor when authoring is needed. Claude Code users must use specforge-author instead.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-cursor-authorsdd/kairos-development/specforge-qa
Use when a deployed feature on the local k3d cluster needs human-style QA — exploratory API/UI testing against the running system, spec edge-case coverage, security probing, performance baselines, and logging/monitoring verification — producing a findings report that specforge can execute fixes from.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-qasdd/kairos-development/specforge-review-architect
Use when a plan or implemented feature needs holistic architectural oversight — spec alignment, scope creep, over-engineering, AI code smells, cross-phase coherence — as distinct from per-diff domain review. Runs at plan gates, phase spot-checks, and as a whole-feature capstone.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-review-architectsdd/kairos-development/specforge-review-helix
Use when reviewing web/ frontend changes in a specforge run — checks Helix web-component usage, design tokens, theming, accessibility, and Kairos web conventions on a phase diff. Fires only when web/** files changed.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-review-helixsdd/kairos-development/specforge-review-kairos
Use when reviewing backend, schema, event, command, SQL, or messaging changes in a Kairos component within a specforge run — checks Kairos architecture conformance (event-driven interop, data ownership, tenancy, generation pipelines) on a phase diff.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-review-kairossdd/kairos-development/specforge-review-nexus
Use when reviewing changes that touch authorization, security, tenant isolation, deployment charts, API contracts, or AI/LLM routing in a Nexus-platform application — enforces the normative Nexus Authorization Guardrails and platform conventions on a phase diff.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-review-nexussdd/kairos-development/specforge-review-tests
Use when reviewing the test suite of a phase in a specforge run — checks presence and quality across Go unit, godog component/functional, frontend Vitest, and integration layers, hunts test smells, and verifies coverage against the spec's bar. Fires on every phase.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-review-testssdd/kairos-development/specforge-temper
Use at the close of every specforge run to turn recurring finding classes (lens-raised or human-raised) and recurring token/step waste into criticality-ranked, evidence-cited improvement proposals for the suite's own skills/constitution/templates, gated on explicit human approval before anything is applied. Also invoked in `apply` mode once a human approves specific proposals, any time after a `propose` run.
npx -y --registry=http://ifsaiskills.rnd.ifsdevworld.com:4873 ifs-ai-skills@0.5.5 add sdd/kairos-development/specforge-temper