apex-spec-marketplace

Apex Spec System

Version: 2.0.4-beta

A Claude Code plugin providing a specification-driven workflow system for AI-assisted development. Think Github Spec Kit (our source inspiration) simplified.

NEW - Apex Spec System "Open"

Open Skill (https://agentskills.io/home) version of this plugin: https://github.com/moshehbenavraham/apex-spec-system-open

Overview

The Apex Spec System breaks large projects into manageable, well-scoped implementation sessions that fit within AI context windows and human attention spans.

Philosophy: 1 session = 1 spec = 2-4 hours (12-25 tasks) = safe context window of AI

Installation

# Install from local directory
claude --plugin-dir /path/to/apex-spec-system

# Or copy to your plugins directory
cp -r apex-spec-system ~/.claude/plugins/

Requirements

Dependency	Required	Install
jq	Yes	apt install jq or brew install jq
git	Optional	Usually pre-installed

The scripts use jq for JSON parsing. Verify with: bash scripts/check-prereqs.sh --env

Quick Start

1. Install the plugin (see above)

2. Initialize in your project:

   /initspec OR /apex-spec:initspec
   

   This creates the spec system structure in your project.

   Optional but recommended: Customize .spec_system/CONVENTIONS.md with your project's coding standards (naming, structure, error handling, testing philosophy, etc.)

   /createprd OR /apex-spec:createprd OR Manually fill out .spec_system/PRD/PRD.md
   

   Optional: Turn argument or file path into a technical PRD for development. Example: /createprd "a habit trackker app" /createprd @docs/requirements.md

   /createuxprd OR /apex-spec:createuxprd
   

   Optional: Turn design docs into a UX PRD companion document. Example: /createuxprd "social app with feed, profiles, and messaging" /createuxprd @docs/design-spec.md

   /phasebuild OR /apex-spec:phasebuild
   

   This will set up the initial Phase and Sessions for that initial Phase

3. Run the session workflow and repeat until all sessions inside the Phase are completed, thus completing the Phase:

   /plansession OR /apex-spec:plansession    # Analyze, spec, and generate task checklist
   /implement OR /apex-spec:implement        # Start implementation
   /validate OR /apex-spec:validate          # Verify completeness, security & compliance
   /updateprd OR /apex-spec:updateprd        # Mark complete, update system
   

4. Between Phases

   /audit OR /apex-spec:audit                # Local dev tooling (formatter, linter, types, tests, observability, hooks)
   /pipeline OR /apex-spec:pipeline          # CI/CD workflows (quality, build, security, integration, ops)
   /infra OR /apex-spec:infra                # Production infrastructure (health, security, backup, deploy)
   /carryforward OR /apex-spec:carryforward  # Lessons learned, security/compliance records
   /documents OR /apex-spec:documents        # Create, maintain project documentation
   -- Optional but HIGHLY recommended, do manual testing and separate LLM Audit HERE --
   /phasebuild OR /apex-spec:phasebuild      # Set up next Phase and Phase's sessions
   

5. Repeat until all phases complete!

Monorepo Quick Start

The system auto-detects monorepo structures. No special configuration needed.

Brownfield (existing monorepo with code):

/initspec

The system detects workspace configs (pnpm, npm workspaces, turbo, nx, cargo, go, lerna), shows detected packages, and asks you to confirm.

Greenfield (new project, PRD describes multiple services):

/initspec       # Sets monorepo: null (unknown)
/createprd      # Detects multi-package signals in PRD, prompts to confirm

Per-package sessions:

User: /plansession
      "Plan a session for apps/web"

# Claude scopes spec.md and tasks.md to apps/web
# File paths use full repo-root-relative paths (apps/web/src/auth.ts)

Sessions interleave across packages within a phase. A phase completes when all its sessions are done, regardless of which packages they target.

What stays the same:

• Single .spec_system/ at the repo root
• Same session ID format (phaseNN-sessionNN-name)
• Same 13-command workflow
• Single-repo projects see zero change

Features