Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By athola
Follow Spec Driven Development workflows to build features systematically: generate testable specs from descriptions, create dependency-ordered task plans, analyze artifacts for quality and consistency, execute phased TDD implementations with progress tracking, and convert tasks to GitHub issues.
npx claudepluginhub athola/claude-night-market --plugin spec-kitCross-artifact consistency analysis across spec.md, plan.md, and tasks.md after task generation
Generate a custom checklist for the current feature based on user requirements.
Ask targeted questions to resolve spec ambiguities
Create/update project constitution from principle inputs, syncing dependent templates
Execute the implementation plan by processing all tasks from tasks.md
Execute implementation tasks systematically following the task plan with TDD approach and progress tracking. Use when executing implementation tasks from tasks.md, continuing implementation, implementing specific phases, systematic code generation. Do not use when generating tasks - use task-generator agent first. analyzing specs - use spec-analyzer agent. Trigger proactively during /speckit-implement commands.
Analyze specification artifacts for consistency, coverage, and quality issues. Use when checking spec quality, validating spec/plan/tasks alignment, debugging missing requirements, detecting ambiguity or underspecification. Do not use when writing specifications - use spec-writing skill. generating tasks - use task-generator agent. Trigger proactively during /speckit-analyze commands.
Generate dependency-ordered implementation tasks from specification and planning artifacts. Use when generating tasks from spec and plan, breaking down implementation work, creating ordered task lists, starting implementation phase. Do not use when analyzing specifications - use spec-analyzer agent. executing tasks - use implementation-executor agent. Trigger proactively during /speckit-tasks commands.
Create clear, testable specifications from feature descriptions with user stories, acceptance criteria, and success metrics.
Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.
Generate phased, dependency-ordered tasks from specifications with parallelization opportunities and tech-stack patterns.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Specification-driven development workflow: specify → plan → tasks → implement
Specification-Driven Development with Process Discipline for Claude Code
Spec-driven development using GitHub spec-kit methodology. Constitution-first approach with specify, plan, tasks, and implement phases.
Spectacular skills/commands library for spec-anchored development and parallel task execution
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
Autonomous agent orchestrator for full development lifecycles with zero human input, session budget management, and crash recovery
Documentation review, cleanup, and generation with AI slop detection, style learning, and human-quality writing enforcement
Media generation capabilities for terminal recordings (VHS), browser recordings (Playwright), GIF processing, and media composition
Git and workspace operations for active development workflows - commit messages, PR prep, documentation updates, and version management
Modern Python development suite - testing, performance optimization, async patterns, and packaging
A plugin marketplace for Claude Code, Anthropic's agentic coding tool.
Night Market extends Claude Code with 23 plugins covering git workflows, code review, spec-driven development, architecture selection, codebase visualization, autonomous agents, multi-LLM delegation, ML-enhanced scoring, and multi-source research. 161 skills, 146 slash commands, and 50 agents. Each plugin installs independently.
Requires Claude Code 2.1.16+ and Python 3.9+ for hooks. See Requirements for details.
# Add the marketplace
/plugin marketplace add athola/claude-night-market
# Install plugins you need
/plugin install sanctum@claude-night-market # Git workflows
/plugin install pensive@claude-night-market # Code review
/plugin install spec-kit@claude-night-market # Spec-driven dev
# Use them
/prepare-pr # Prepare a pull request
/full-review # Run code review
Alternative: Install via npx with
npx skills add athola/claude-night-market (installs all plugins at once).
After installation, run claude --init for one-time setup.
Note: If the
Skilltool is unavailable, read skill files directly atplugins/{plugin}/skills/{skill-name}/SKILL.md.
# Install specific plugins
opkg i gh@athola/claude-night-market --plugins sanctum
opkg i gh@athola/claude-night-market --plugins pensive,conserve
# Plugins that depend on shared runtime skills (e.g. attune, conjure)
# automatically pull packages/core as a dependency
See the Installation Guide for detailed setup options.
23 plugins organized in four layers. Domain specialists depend on utility plugins, which depend on foundation plugins, which depend on the meta layer.
flowchart TB
classDef domainClass fill:#e8f4f8,stroke:#2980b9,stroke-width:2px,color:#2c3e50
classDef utilityClass fill:#f8f4e8,stroke:#f39c12,stroke-width:2px,color:#2c3e50
classDef foundationClass fill:#f4e8f8,stroke:#8e44ad,stroke-width:2px,color:#2c3e50
classDef metaClass fill:#e8f4e8,stroke:#27ae60,stroke-width:2px,color:#2c3e50
subgraph Domain["Domain Specialists"]
direction LR
D1[archetypes]:::domainClass
D2[pensive]:::domainClass
D3[parseltongue]:::domainClass
D4[memory-palace]:::domainClass
D5[spec-kit]:::domainClass
D6[minister]:::domainClass
D7[attune]:::domainClass
D8[scry]:::domainClass
D9[scribe]:::domainClass
D10[tome]:::domainClass
D11[gauntlet]:::domainClass
D12[cartograph]:::domainClass
end
subgraph Utility["Utility Layer"]
direction LR
U1[conserve]:::utilityClass
U2[conjure]:::utilityClass
U3[hookify]:::utilityClass
U4[egregore]:::utilityClass
U5[herald]:::utilityClass
U6[oracle]:::utilityClass
end
subgraph Foundation["Foundation Layer"]
direction LR
F1[imbue]:::foundationClass
F2[sanctum]:::foundationClass
F3[leyline]:::foundationClass
end
subgraph Meta["Meta Layer"]
direction LR
M1[abstract]:::metaClass
end
Domain ==> Utility ==> Foundation ==> Meta