claude

spec-driven-dev

Spec-driven development with structured directories, borrowing ideas from Kiro and Spec-kit

0 on GitHubby a3lemv1.0.0updated 24 days ago
/

Plugin spec-driven-dev from marketplace a3lem-claude-plugins in a3lem/my-claude-plugins. Commands read from the repo's manifest — 23 days ago.

What it installs

Skills (1)

  • spec-driven-development

    Spec-driven development workflow. Use for exploring ideas, proposing changes, implementing specs, and archiving completed work. Triggers on "spec", "propose", "explore", "apply", "archive", "critique", or "specification".

Slash commands (5)

  • /spec-driven-dev:apply
  • /spec-driven-dev:archive
  • /spec-driven-dev:explore
  • /spec-driven-dev:propose
  • /spec-driven-dev:refine

Subagents (2)

  • spec-critic

    Reviews and challenges specifications and implementation. Acts as senior engineer stand-in. Engages in multi-turn dialogue until satisfied.

  • spec-sync

    Merges spec deltas into reference specs during the archive phase. Handles ADDED, MODIFIED, REMOVED, and RENAMED operations across all capabilities in a change.

View source on GitHub

More from a3lem/my-claude-plugins

All 12 plugins →

Persistent auto-memory across sessions with configurable storage location

2 commands · hooks

0

Project knowledge management with notes, decision logs, and timestamped journal entries

3 skills

0

Integration for the tk CLI ticket system - git-backed issue tracking for AI agents

1 skill · hooks

0

Structured [AI] comment blocks with provenance, context, intent, and assumptions for meaningful code review

hooks

0

Manage AI provenance metadata blocks in source files to track review status, rule references, and access control

1 skill

0

Maintain spec-driven-dev?

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.

claude & codex plugins12 plugins