Nagiliant

25 mods across 1 repository, 2 stars between them.

genesis-spec-kit

02

Nagiliant/Genesis-Legacy-V2

Plugin Claude Code

AI coding with intent — the end of vibe coding. A spec-driven pipeline for Claude Code that loops a five-lens audit to zero findings before code ships. It won't save you time or tokens; it saves you from slop. File-backed, no external services. Legacy (V2-era) edition.

2 2mo ago A tokens not measured original Apache-2.0

A2 — Spec Review

04

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.

2 2mo ago A 39 tokens original Apache-2.0

A3 — Polish

05

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.

2 2mo ago A 48 tokens original Apache-2.0

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.

2 2mo ago A 48 tokens original Apache-2.0

A5 — Web Audit

07

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.

2 2mo ago A 46 tokens original Apache-2.0

Accept

08

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.

2 2mo ago A 36 tokens original Apache-2.0

Amend

09

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Formally amend the constitution, with mandatory impact analysis before any change lands. The constitution is supreme law; amendments are versioned and their downstream effects scanned first.

2 2mo ago A 35 tokens original Apache-2.0

Brainstorm

10

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Interactive ideation and decision capture at any pipeline boundary. Opinionated dialogue that surfaces contradictions, gaps, and untested assumptions — not template-filling. Feeds the Furnace.

2 2mo ago A 38 tokens original Apache-2.0

Clarify

11

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Find and close holes in the master spec before the North Star — resolve ambiguity markers, run a coverage scan, ask high-impact questions, and optionally simulate usage scenarios.

2 2mo ago A 36 tokens original Apache-2.0

Closure

12

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Git closure — push the branch and open a PR. The ONLY step that performs git operations. Never auto-merges.

2 2mo ago A 26 tokens original Apache-2.0

Constitute

13

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Create or amend the constitution — the project's supreme, enforceable law. Everything built afterward must comply.

2 2mo ago A 23 tokens original Apache-2.0

Design

14

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Author project-level design documentation — architecture, data models, API contracts, user journeys, glossaries, and decision records (ADRs). For per-feature design, use /genesis-feature.

2 2mo ago A 40 tokens original Apache-2.0

Discover

15

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Build the project profile through guided conversation — the grounding document every later phase reads. Establishes the mode and, for content projects, the work-unit registry.

2 2mo ago A 33 tokens original Apache-2.0

Feature

16

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Write the feature design doc — the WHY + SHAPE for a single feature. No formal requirements yet (those come in /genesis-specify).

2 2mo ago A 32 tokens original Apache-2.0

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

The feature-wide final audit. Re-runs the five lenses across ALL groups together, then two extra passes — Dreamland (dream perfection, then make it real) and Simulation (realistic scale testing). Runs after every group is accepted.

2 2mo ago A 55 tokens original Apache-2.0

Help

18

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Command reference for Genesis Spec-Kit. Pass a command name for detailed help on that command.

2 2mo ago A 21 tokens original Apache-2.0

Implement

19

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Implement one micro spec — one commit, one PR. The micro spec is the complete instruction set; write only the files in its File Operations table, verify against its acceptance criteria, commit.

2 2mo ago A 40 tokens original Apache-2.0

Init

20

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Initialize Genesis Spec-Kit in a project — scaffold .genesis/ and determine the project mode (greenfield, brownfield, lowfield). Use when setting up the kit for the first time.

2 2mo ago A 42 tokens original Apache-2.0

Micro

21

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Write all micro specs for one group — fully self-contained implementation units, plus the group's simulation scenarios and human-testing checklist.

2 2mo ago A 26 tokens original Apache-2.0

North Star

22

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Write the perfect-world vision for the feature — no-compromise narrative, weighted quality dimensions, and the Compass. The qualitative reference every audit measures against.

2 2mo ago A 33 tokens original Apache-2.0

Resume

23

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Reconstruct the exact pipeline position from disk, load the frontier spec in full, list failed approaches not to retry, and present the next action. Read-only, any time.

2 2mo ago A 37 tokens original Apache-2.0

Specify

24

Nagiliant/Genesis-Legacy-V2

Skill Claude CodeCodex

Write the master spec — the WHAT. User stories, functional & non-functional requirements, acceptance criteria, and the dependency-ordered micro-spec plan. Strictly WHAT, never HOW.

2 2mo ago A 38 tokens original Apache-2.0