102 tagged spec driven, measured the same way as everything else here.
Browse within: sdd 54engineering 48novels 48spec 48spec-driven-development 17process 15software-development 15subagents 15pdca 12Code Generation 10ai-assisted-development 9nextjs 9postgresql 9prisma 9
Command
A command that turns book-analysis reports into reusable writing guidance for a Novel Writer project. It creates style, structure, and rhythm configuration files that later writing commands can use.
Command
A command for analysing how a novel is written, including its descriptions, actions, character thoughts, and dialogue.
Command
A command for managing active sessions in a writing service called Stardust, including viewing their details and status. A session is a temporary workspace or connection used to carry out a task.
Command
Deep, pre-merge review of a PR / branch / diff at three strengths — quick / default (default) / deep — one verdict, posted to GitHub when a PR number is given. Decides whether a change is safe to ship with evidence-backed findings, rather than a shallow "looks good" pass. Produces a ship it / needs fixes / blocked…
Command
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…
Command
Start a new harness iteration — optional direction hint, research, grill-me, compass/plans, Review & Edit chain (long-lived {SPECSDIR}/ + {ITERATIONDIR}/ / package; compound promotes package at close only), PM lock, integration branch; then auto-continue Phase 2→5 (execute → close → PR → merge-ready) unless pause arg…
lindoelio/spec-driven-steroids
Command
Generate or refresh repository guideline documents using the project-guidelines-writer skill. Analyze the repo, generate all six standard guideline files by default, prefer managed-section updates for existing files, and ask only for exceptional overwrite or skip decisions.
lindoelio/spec-driven-steroids
Command
Start an approved Spec-Driven workflow using the brief or full lane.
Command
Analyze existing modern codebase to understand architecture, patterns, and conventions before adding new features.
Command
Execute end-to-end tests based on the E2E test plan and generate detailed test result reports.
Command
Execute the standardization workflow to create comprehensive coding standards and conventions documentation for the entire product.
Command
Step 3 of the Vibe-Spec workflow. Break the V1 spec into sequential, self-contained phases and append a phase index, producing the final V2 spec.
Command
Step 4 of the Vibe-Spec workflow. Generate the high-level plan file for every phase in the V2 phase index, each with a scope + status header, so the user has a complete set of plan files to work from.
Command
Audit a Vibe-Spec app for secrets leaking to the browser. A locked-down, redacting command — a local script reads .env and the built bundle, and Claude only ever sees variable NAMES and pass/fail verdicts. Secret values never enter the model's context.
Command
Execute project-act through Core-owned bounded WorkUnits.
Command
Execute project-check through Core-owned bounded WorkUnits.
Command
Analyze requirements, create Spec and Story through bounded WorkUnits.
Command
Starts a new end-to-end need (preflight, team, spawn OR).
Command Claude Code
You are a Principal Engineer & Product Architect conducting a full adversarial audit of this codebase. Your job is not to be polite. Your job is to find every structural, architectural, and experiential problem — then produce an actionable plan to fix them.
Command
Generate a visual design (prototype | walkthrough | canvas) + design-spec.md for a feature, BEFORE decomposition.
Command
Run the DEV Phase pipeline for a feature (frontend + backend agents per task, then qa, devops, doc-gen, then snapshot).