Specs-driven development: write the product specs before the code. prd: a product requirements document with numbered requirements. nfr: measurable quality targets for those requirements. use-case: fully dressed use cases traced to those requirements. acceptance-criteria: Gherkin scenarios traced to the use cases, ready to drive tests.
0 on GitHubby Alex Cristeav0.1.0MITupdated 20 days ago
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Write acceptance criteria as Gherkin scenarios (Given / When / Then) for a feature or use case, one scenario per main path and per extension, each tagged with a stable ID (AC-01.1) and traced to its use case (UC-01) and requirements (FR-1), saved as specs/<feature>/acceptance/UC-01-<slug>.feature so
nfr
Write or update one-page non-functional requirements (NFRs) for a feature or product: quality targets for performance, availability, security, privacy, accessibility, usability and compliance, each with a stable ID (NFR-1), a measurable target, how it is verified and the requirements (FR-1) it appli
prd
Write or update a one-page product requirements document (PRD) for a feature or product: a one-sentence summary, the problem and its evidence, goals and non-goals, who it is for, numbered functional requirements (FR-1), success metrics with a guardrail, risks and open questions, saved as specs/<feat
use-case
Write one-page fully dressed use cases (Cockburn style) for a feature: primary actor, goal, preconditions, guarantees, a numbered main success scenario and extensions for every step that can fail, each traced to the PRD requirements (FR-1) it covers, saved as specs/<feature>/use-cases/UC-01-<slug>.m
Work with Clay from Claude Code: set up and sign in to the clay CLI, query and analyze Clay tables, search Clay's GTM database for people and companies, manage audiences, signals, routines and workflows, and draft and review Sequencer campaigns. Includes hooks that auto-approve the plugin's own clay CLI calls and Clay skills; requires a Clay account.
Require a human approval signal before an AI agent can post PR reviews, comments, merges, or writes to CI configuration. Joins protect-mcp and signed-audit-trails in the governance category; composes with protect-mcp for runtime enforcement.
Evidence-backed BioPharma research workflows over Maven Bio's drug, trial, company, and deal knowledge graph. Skills for competitive pipelines, indication landscapes, asset profiles, deal and financing activity, and evidence synthesis grounded in FDA, SEC, clinical, and press sources. Requires a Maven Bio account.
Real-time statusline showing context usage, active tools, running agents, and todo progress. Always visible below your input, zero config required.
1 skill
jarrodwatts/claude-hud 29,182
Maintain specs?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.