specweave 0.1.7 → 0.1.9

package/src/commands/create-increment.md

@@ -1,223 +0,0 @@
----
-name: create-increment
-description: Create a new SpecWeave increment interactively with spec.md and tasks.md
----
-
-# Create New Increment
-
-You are helping the user create a new SpecWeave increment.
-
-## Steps:
-
-1. **Find next increment number**:
-   - Scan `.specweave/increments/` directory
-   - Find highest number (e.g., 002)
-   - Next increment: 003
-
-2. **Detect tech stack** (CRITICAL - framework-agnostic):
-   - Check `.specweave/config.yaml` for tech_stack configuration
-   - If not found, detect from project files:
-     - `package.json` → TypeScript/JavaScript
-     - `requirements.txt` or `pyproject.toml` → Python
-     - `go.mod` → Go
-     - `Cargo.toml` → Rust
-     - `pom.xml` or `build.gradle` → Java
-     - `*.csproj` → C#/.NET
-   - Detect framework (NextJS, Django, FastAPI, Spring Boot, etc.)
-   - If detection fails, ask user: "What language/framework are you using?"
-   - Store detected tech stack for later use
-
-3. **Ask user for details**:
-   - "What would you like to build?" (get high-level description)
-   - "What's the short name?" (e.g., "user-authentication" for increment 003-user-authentication)
-   - "Priority? (P1/P2/P3)" (default: P1)
-
-4. **Activate role-orchestrator**:
-   - Analyze user's description
-   - Determine which strategic agents are needed:
-     - pm-agent (product strategy)?
-     - architect-agent (system design)?
-     - devops-agent (infrastructure)?
-     - security-agent (security review)?
-     - qa-lead-agent (testing strategy)?
-
-5. **Ask clarifying questions** (if needed):
-   - Target users/scale?
-   - Technology preferences? (if not detected)
-   - Budget constraints?
-   - Deployment platform?
-   - Payment processing needed?
-   - Authentication method?
-
-6. **Run strategic agents** (with user approval):
-   - **Pass detected tech stack to ALL agents** (CRITICAL!)
-   - PM agent creates pm-analysis.md
-   - Architect agent creates architecture.md, ADRs (using detected tech stack)
-   - DevOps agent creates infrastructure.md (platform-specific)
-   - Security agent creates security.md (framework-specific security)
-   - QA agent creates test-strategy.md (framework-specific tests)
-
-7. **Present strategic docs for review**:
-   - Show summary of all strategic outputs
-   - Ask: "Review docs with /review-docs or approve to continue?"
-   - Wait for user approval
-
-8. **Create spec.md** (based on strategic docs):
-   - Frontmatter with increment number, title, priority, status, dependencies
-   - **Include detected tech stack in frontmatter** (see format below)
-   - Overview section
-   - Business value
-   - User stories with acceptance tests
-   - Functional requirements
-   - Out of scope
-   - Success criteria
-   - Dependencies
-
-9. **Create tasks.md** (task-builder skill):
-   - Analyze all strategic docs
-   - Break down into phases (framework-specific)
-   - Create tasks with:
-     - Agent references (use framework-specific agents if available)
-     - File paths (framework-specific paths: src/ for TS, app/ for Django, etc.)
-     - Implementation snippets (framework-specific code)
-     - Acceptance criteria
-     - Documentation updates
-
-10. **Save increment**:
-    - Create `.specweave/increments/####-name/`
-    - Save spec.md
-    - Save tasks.md
-    - Save strategic docs (pm-analysis.md, architecture.md, etc.)
-
-11. **Output to user**:
-    ```
-    ✅ Created increment 0003-user-authentication
-
-       Detected tech stack:
-       - Language: {detected-language} (e.g., Python, TypeScript, Go, Java)
-       - Framework: {detected-framework} (e.g., Django, FastAPI, NextJS, Spring Boot)
-       - Database: {specified-database} (e.g., PostgreSQL, MySQL, MongoDB)
-       - Platform: {specified-platform} (e.g., AWS, Hetzner, Vercel, self-hosted)
-
-       Location: .specweave/increments/0003-user-authentication/
-
-       📋 Files created:
-       - spec.md (6 user stories, 15 requirements)
-       - tasks.md (42 implementation tasks using {framework} patterns)
-       - pm-analysis.md (product strategy)
-       - architecture.md (system design for {framework})
-       - infrastructure.md ({platform} deployment)
-       - security.md ({framework}-specific security)
-       - test-strategy.md (E2E tests for {framework})
-
-       ⏱️  Estimated effort: 3-4 weeks
-
-       Next steps:
-       1. Review docs: /review-docs
-       2. Start implementation: Begin with Task T001 in tasks.md
-       3. Sync to GitHub: /sync-github
-    ```
-
-## Frontmatter Format (spec.md):
-
-**IMPORTANT**: Tech stack is DETECTED from `.specweave/config.yaml` or project files, NOT hardcoded!
-
-```yaml
----
-increment: 003-user-authentication
-title: "User Authentication System"
-priority: P1
-status: planned
-created: 2025-10-26
-dependencies: []
-structure: user-stories
-
-# Tech stack is DETECTED, not hardcoded
-tech_stack:
-  detected_from: ".specweave/config.yaml"  # or "package.json", "requirements.txt", etc.
-  language: "{detected-language}"          # e.g., "typescript", "python", "go", "java", "rust"
-  framework: "{detected-framework}"        # e.g., "nextjs", "django", "fastapi", "spring-boot", "gin"
-  database: "{specified-database}"         # e.g., "postgresql", "mysql", "mongodb", "sqlite"
-  orm: "{detected-orm}"                    # e.g., "prisma", "django-orm", "sqlalchemy", "hibernate"
-
-# Platform is SPECIFIED by user or detected from config
-platform: "{specified-platform}"           # e.g., "hetzner", "aws", "vercel", "self-hosted"
-estimated_cost: "{calculated-based-on-platform}"
----
-```
-
-**Example for TypeScript/NextJS project**:
-```yaml
-tech_stack:
-  detected_from: "package.json"
-  language: "typescript"
-  framework: "nextjs"
-  database: "postgresql"
-  orm: "prisma"
-platform: "vercel"
-estimated_cost: "$20/month"
-```
-
-**Example for Python/Django project**:
-```yaml
-tech_stack:
-  detected_from: "requirements.txt"
-  language: "python"
-  framework: "django"
-  database: "postgresql"
-  orm: "django-orm"
-platform: "hetzner"
-estimated_cost: "$12/month"
-```
-
-**Example for Go/Gin project**:
-```yaml
-tech_stack:
-  detected_from: "go.mod"
-  language: "go"
-  framework: "gin"
-  database: "postgresql"
-  orm: "gorm"
-platform: "aws"
-estimated_cost: "$25/month"
-```
-
-## Frontmatter Format (tasks.md):
-
-```yaml
----
-increment: 003-event-booking-saas
-status: planned
-dependencies:
-  - 001-skills-framework
-  - 002-role-based-agents
-phases:
-  - infrastructure
-  - backend
-  - frontend
-  - testing
-  - deployment
-estimated_tasks: 42
-estimated_weeks: 3-4
----
-```
-
-## Autonomous Mode (Advanced):
-
-If user says "autonomous mode" or "full automation":
-1. Run all strategic agents
-2. Create increment
-3. **Start implementation immediately** (with permission)
-4. Ask clarification questions only when critical
-5. Suggest doc updates when needed
-6. Complete full implementation autonomously
-
-## Error Handling:
-
-- If `.specweave/` not found: "Error: Not a SpecWeave project. Run /create-project first."
-- If user description too vague: Ask more clarifying questions
-- If strategic agents not available: "Warning: Some agents missing. Continue with basic spec?"
-
----
-
-**Important**: This is the main entry point for creating new work in SpecWeave.

package/src/commands/init.md

@@ -1,123 +0,0 @@
----
-description: 🔥 Shorthand for /create-project - Initialize SpecWeave project (Alias)
----
-
-# Initialize Project (Short Alias)
-
-**⚡ Quick Alias**: This is a shorthand command for `/create-project`.
-
-Use this when you want to quickly initialize a new SpecWeave project without typing the full command name.
-
----
-
-## Full Command
-
-For complete documentation, see `/create-project`.
-
-This alias provides the exact same functionality as the full command.
-
----
-
-## Usage
-
-```bash
-/init [project-name] [--type=<stack>]
-```
-
-**Examples**:
-```bash
-/init                           # Interactive prompts
-/init my-saas                   # Auto-detect tech stack
-/init my-api --type=python      # Specify Python
-/init my-app --type=nextjs      # Specify Next.js
-```
-
----
-
-## What This Does
-
-1. **Creates directory structure**:
-   ```
-   my-project/
-   ├── .specweave/
-   │   ├── config.yaml
-   │   ├── docs/
-   │   ├── increments/
-   │   └── tests/
-   ├── .claude/
-   │   ├── commands/
-   │   ├── skills/      # Auto-install on demand
-   │   └── agents/      # Auto-install on demand
-   ├── CLAUDE.md
-   └── README.md
-   ```
-
-2. **Detects tech stack** (or uses `--type` flag):
-   - TypeScript/JavaScript → Next.js, Node.js, React
-   - Python → FastAPI, Django, Flask
-   - Go → Gin, Echo, standard library
-   - .NET → ASP.NET Core
-   - Java → Spring Boot
-
-3. **Auto-installs components** based on your first request:
-   ```
-   User: "Create Next.js authentication"
-
-   📦 Installing required components...
-      ✅ nextjs skill
-      ✅ nodejs-backend skill
-      ✅ security agent
-      ✅ pm agent
-   ```
-
-4. **Initializes git** (if git available)
-
-5. **Shows next steps**
-
----
-
-## Tech Stack Detection
-
-**Auto-detected from**:
-- `package.json` (JavaScript/TypeScript)
-- `requirements.txt`, `pyproject.toml` (Python)
-- `go.mod` (Go)
-- `*.csproj` (.NET)
-- `pom.xml`, `build.gradle` (Java)
-
-**Manual specification**:
-```bash
-/init --type=nextjs      # Next.js + TypeScript
-/init --type=python      # Python (FastAPI default)
-/init --type=django      # Django specifically
-/init --type=dotnet      # ASP.NET Core
-```
-
----
-
-## After Initialization
-
-**Start building immediately**:
-```bash
-cd my-project
-/ci "User authentication"    # Create first increment
-```
-
-SpecWeave will:
-1. Detect you need auth components
-2. Auto-install: `security` agent, `nodejs-backend` skill
-3. Generate specs, plan, tasks
-4. Ready to implement!
-
----
-
-## Other Useful Aliases
-
-- `/ci` - Create increment (shorthand for `/create-increment`)
-- `/si` - Start increment (shorthand for `/start-increment`)
-- `/vi` - Validate increment (shorthand for `/validate-increment`)
-- `/ls` - List increments (shorthand for `/list-increments`)
-
----
-
-**💡 Tip**: No need to pre-install components - they install on-demand!

package/src/commands/ls.md

@@ -1,100 +0,0 @@
----
-description: 🔥 Shorthand for /list-increments - List all increments (Alias)
----
-
-# List Increments (Short Alias)
-
-**⚡ Quick Alias**: This is a shorthand command for `/list-increments`.
-
-Use this when you want to quickly list increments without typing the full command name.
-
----
-
-## Full Command
-
-For complete documentation, see `/list-increments`.
-
-This alias provides the exact same functionality as the full command.
-
----
-
-## Usage
-
-```bash
-/ls [--status=<status>] [--format=<format>]
-```
-
-**Examples**:
-```bash
-/ls                          # All increments
-/ls --status=in-progress     # Only in-progress
-/ls --status=planned         # Only planned
-/ls --format=detailed        # Detailed view
-```
-
----
-
-## What This Shows
-
-**Default View** (Summary):
-```
-📋 SpecWeave Increments
-
-Status: in-progress (2) | planned (3) | completed (5) | closed (4)
-
-In Progress:
-  0012-user-authentication     [████████░░] 80% (8/10 tasks)
-  0013-payment-integration     [███░░░░░░░] 30% (3/10 tasks)
-
-Planned:
-  0014-admin-dashboard         [░░░░░░░░░░]  0% (0/15 tasks)
-  0015-analytics-module        [░░░░░░░░░░]  0% (0/12 tasks)
-```
-
-**Detailed View** (`--format=detailed`):
-Shows full spec summary, architecture approach, test coverage, etc.
-
----
-
-## Status Filters
-
-| Status | Description | Alias |
-|--------|-------------|-------|
-| `backlog` | Not yet planned | Ideas, proposals |
-| `planned` | Spec created, not started | Ready to work |
-| `in-progress` | Active work | Currently implementing |
-| `completed` | Tasks done, ready to close | Awaiting review/merge |
-| `closed` | Finished and archived | Done |
-
----
-
-## Typical Usage
-
-**Quick check**:
-```bash
-/ls --status=in-progress     # What am I working on?
-```
-
-**Planning**:
-```bash
-/ls --status=planned         # What's next?
-```
-
-**Review**:
-```bash
-/ls --format=detailed        # Full increment overview
-```
-
----
-
-## Other Useful Aliases
-
-- `/ci` - Create increment (shorthand for `/create-increment`)
-- `/si` - Start increment (shorthand for `/start-increment`)
-- `/vi` - Validate increment (shorthand for `/validate-increment`)
-- `/done` - Close increment (shorthand for `/close-increment`)
-- `/at` - Add tasks (shorthand for `/add-tasks`)
-
----
-
-**💡 Tip**: Use `/ls` daily to track progress across all increments.

package/src/commands/pi.md

@@ -1,65 +0,0 @@
----
-description: 🔥 Shorthand for /create-increment - Plan Product Increment (Alias)
----
-
-# Plan Product Increment (Short Alias)
-
-**⚡ Quick Alias**: This is a shorthand command for `/create-increment`.
-
-**PI = Product Increment** - Standard Agile terminology for a planned unit of work.
-
-Use this when you want to quickly create a new SpecWeave increment without typing the full command name.
-
----
-
-## Full Command
-
-For complete documentation, see `/create-increment`.
-
-This alias provides the exact same functionality as the full command.
-
----
-
-## Usage
-
-```bash
-/pi "Feature name"
-```
-
-**Example**:
-```bash
-/pi "User authentication"
-/pi "Payment processing"
-/pi "Admin dashboard"
-```
-
----
-
-## What This Does
-
-1. **Auto-numbers** the increment (e.g., 0001, 0002, 0003...)
-2. **Creates folder** at `.specweave/increments/XXXX-feature-name/`
-3. **Generates files**:
-   - `spec.md` - WHAT & WHY (user stories, acceptance criteria)
-   - `plan.md` - HOW (architecture, implementation strategy)
-   - `tasks.md` - Implementation checklist
-   - `tests.md` - Test strategy and coverage matrix
-   - `context-manifest.yaml` - Context loading configuration
-4. **Invokes agents**:
-   - PM agent (requirements analysis)
-   - Architect agent (technical design)
-   - QA Lead agent (test strategy)
-
----
-
-## Other Useful Aliases
-
-- `/si` - Start increment (shorthand for `/start-increment`)
-- `/vi` - Validate increment (shorthand for `/validate-increment`)
-- `/done` - Close increment (shorthand for `/close-increment`)
-- `/ls` - List increments (shorthand for `/list-increments`)
-- `/at` - Add tasks (shorthand for `/add-tasks`)
-
----
-
-**💡 Tip**: Use `/pi` for speed (PI = Product Increment in Agile), `/create-increment` for clarity in scripts.

package/src/commands/si.md

@@ -1,83 +0,0 @@
----
-description: 🔥 Shorthand for /start-increment - Start working on increment (Alias)
----
-
-# Start Increment (Short Alias)
-
-**⚡ Quick Alias**: This is a shorthand command for `/start-increment`.
-
-Use this when you want to quickly start working on an increment without typing the full command name.
-
----
-
-## Full Command
-
-For complete documentation, see `/start-increment`.
-
-This alias provides the exact same functionality as the full command.
-
----
-
-## Usage
-
-```bash
-/si <increment-id>
-```
-
-**Examples**:
-```bash
-/si 0001
-/si 0042
-/si 0123
-```
-
----
-
-## What This Does
-
-1. **Updates status** to `in-progress` in `tasks.md`
-2. **Loads context** via context-manifest.yaml
-3. **Creates feature branch** (if git workflow enabled)
-4. **Shows increment summary**:
-   - Spec highlights (user stories, goals)
-   - Architecture approach
-   - Task breakdown
-   - Test strategy
-
----
-
-## Typical Workflow
-
-```bash
-# 1. Create increment
-/ci "User authentication"
-
-# 2. Review generated specs
-# ... check spec.md, plan.md, tasks.md ...
-
-# 3. Start working
-/si 0001
-
-# 4. Implement tasks
-# ... write code, tests, docs ...
-
-# 5. Validate quality
-/vi 0001 --quality
-
-# 6. Close when done
-/done 0001
-```
-
----
-
-## Other Useful Aliases
-
-- `/ci` - Create increment (shorthand for `/create-increment`)
-- `/vi` - Validate increment (shorthand for `/validate-increment`)
-- `/done` - Close increment (shorthand for `/close-increment`)
-- `/ls` - List increments (shorthand for `/list-increments`)
-- `/at` - Add tasks (shorthand for `/add-tasks`)
-
----
-
-**💡 Tip**: Always validate (`/vi`) before starting to catch spec issues early.