lean-spec 0.1.0

package/templates/enterprise/spec-template.md

@@ -0,0 +1,75 @@
+---
+status: planned
+created: {date}
+tags: []
+priority: medium
+assignee: 
+reviewer: 
+related: []
+issue: 
+epic: 
+---
+
+# {name}
+
+> **Status**: 📅 Planned · **Priority**: Medium · **Created**: {date}  
+> **Assignee**: TBD · **Reviewer**: TBD
+
+## Overview
+
+<!-- What business problem? Why now? Expected impact? -->
+
+## Research
+
+<!-- Background investigation, alternatives evaluated, key findings -->
+
+## Design
+
+<!-- Architecture, system interactions, data flows -->
+
+### Dependencies
+
+- **Teams**: <!-- Which teams need to coordinate? -->
+- **Systems**: <!-- External systems affected -->
+- **Data**: <!-- Databases, APIs, shared resources -->
+
+### Security & Compliance
+
+- [ ] Handles sensitive data (PII, credentials, etc.)
+- [ ] Security implications reviewed
+- [ ] Compliance requirements identified
+
+## Plan
+
+<!-- Break into phases if needed -->
+
+- [ ] Task 1 - @owner
+- [ ] Task 2 - @owner
+- [ ] Task 3 - @owner
+
+## Test
+
+<!-- How to verify correctness and safety -->
+
+- [ ] Unit/integration tests
+- [ ] Load/performance testing
+- [ ] Security testing
+- [ ] Rollback plan
+
+## Risks
+
+| Risk | Impact | Mitigation |
+|------|--------|------------|
+|      |        |            |
+
+## Rollout
+
+<!-- Deployment strategy for production systems -->
+
+- Staging validation: 
+- Production approach: 
+- Monitoring: 
+
+## Notes
+
+<!-- Key decisions, constraints, unresolved questions -->

package/templates/minimal/README.md

@@ -0,0 +1,18 @@
+# Minimal Template
+
+Bare essentials. Just the spec folder structure, nothing else.
+
+## What's Included
+
+- Spec folder structure (`specs/YYYYMMDD/NNN-name/`)
+- That's it
+
+## When to Use
+
+- You want maximum flexibility
+- Adding LeanSpec to existing project with established practices
+- Don't need AI agent instructions
+
+## Next Steps
+
+Create your first spec: `lspec create my-feature`

package/templates/minimal/config.json

@@ -0,0 +1,14 @@
+{
+  "name": "Minimal",
+  "description": "Just the essentials - folder structure only",
+  "config": {
+    "template": "minimal",
+    "specsDir": "specs",
+    "structure": {
+      "pattern": "{date}/{seq}-{name}/",
+      "dateFormat": "YYYYMMDD",
+      "sequenceDigits": 3,
+      "defaultFile": "README.md"
+    }
+  }
+}

package/templates/minimal/files/AGENTS.md

@@ -0,0 +1,76 @@
+# AI Agent Instructions
+
+## Project: {project_name}
+
+Lightweight spec methodology for AI-powered development.
+
+## Core Rules
+
+1. **Read README.md first** - Understand project context
+2. **Check specs/** - Review existing specs before starting
+3. **Follow LeanSpec principles** - Clarity over documentation
+4. **Keep it minimal** - If it doesn't add clarity, cut it
+
+## When to Use Specs
+
+- Features that affect multiple parts of the system
+- Breaking changes or significant refactors
+- Design decisions that need thinking through
+- Complex features that benefit from upfront planning
+
+Skip specs for:
+- Bug fixes
+- Trivial changes
+- Self-explanatory refactors
+
+## Discovery Commands
+
+Before starting work, understand project context:
+
+- `lspec stats` - See work distribution
+- `lspec board` - View specs by status
+- `lspec search "<query>"` - Find relevant work
+- `lspec list` - List all specs
+
+These help you understand what exists and what's in progress.
+
+## Spec Frontmatter
+
+When creating or updating specs, add YAML frontmatter at the top:
+
+```yaml
+---
+status: draft|planned|in-progress|complete|blocked|cancelled
+created: YYYY-MM-DD
+---
+```
+
+**Keep it simple:**
+- Just `status` and `created` fields
+- Other fields are optional - only add if helpful
+- Update `status` as work progresses
+
+**Update status with:**
+```bash
+lspec update <spec> --status in-progress
+```
+
+## Workflow
+
+1. **Check existing work** - Run `lspec board` or `lspec search`
+2. **Create or update spec** - Add frontmatter with `status` and `created`
+3. **Implement changes** - Keep spec in sync as you learn
+4. **Update status** - Mark progress: `draft` → `in-progress` → `complete`
+5. **Archive when done** - `lspec archive <spec>` moves to archive
+
+## Quality Standards
+
+- Code is clear and maintainable
+- Tests cover critical paths
+- No unnecessary complexity
+- Documentation where needed (not everywhere)
+- Specs stay in sync with implementation
+
+---
+
+**Remember**: LeanSpec is a mindset. Adapt these guidelines to what actually helps.

package/templates/minimal/spec-template.md

@@ -0,0 +1,25 @@
+---
+status: planned
+created: {date}
+---
+
+# {name}
+
+> **Status**: 📅 Planned · **Created**: {date}
+
+## Goal
+
+<!-- What problem does this solve? Why now? -->
+
+## Key Points
+
+- 
+- 
+
+## Non-Goals
+
+- 
+
+## Notes
+
+<!-- Decisions, constraints, open questions -->

package/templates/standard/README.md

@@ -0,0 +1,24 @@
+# Standard Template
+
+Recommended for most projects. Includes AI agent instructions and sensible defaults.
+
+## What's Included
+
+- **AGENTS.md** - Instructions for AI coding assistants
+- Spec folder structure
+- Opinionated defaults for fast iteration
+
+## When to Use
+
+- Solo developers or small teams
+- Want AI agent integration
+- Need clear but not heavy-weight process
+
+## Philosophy
+
+Keep it lean. Write specs for features that need clarity. Skip them for obvious changes.
+
+## Next Steps
+
+1. Customize AGENTS.md for your project
+2. Create your first spec: `lspec create my-feature`

package/templates/standard/config.json

@@ -0,0 +1,17 @@
+{
+  "name": "Standard",
+  "description": "Recommended for most projects - solo devs and small teams",
+  "config": {
+    "template": "standard",
+    "specsDir": "specs",
+    "structure": {
+      "pattern": "{date}/{seq}-{name}/",
+      "dateFormat": "YYYYMMDD",
+      "sequenceDigits": 3,
+      "defaultFile": "README.md"
+    },
+    "features": {
+      "aiAgents": true
+    }
+  }
+}

package/templates/standard/files/AGENTS.md

@@ -0,0 +1,84 @@
+# AI Agent Instructions
+
+## Project: {project_name}
+
+Lightweight spec methodology for AI-powered development.
+
+## Core Rules
+
+1. **Read README.md first** - Understand project context
+2. **Check specs/** - Review existing specs before starting
+3. **Follow LeanSpec principles** - Clarity over documentation
+4. **Keep it minimal** - If it doesn't add clarity, cut it
+
+## When to Use Specs
+
+- Features that affect multiple parts of the system
+- Breaking changes or significant refactors
+- Design decisions that need team alignment
+- Complex features that benefit from upfront thinking
+
+Skip specs for:
+- Bug fixes
+- Trivial changes
+- Self-explanatory refactors
+
+## Discovery Commands
+
+Before starting work, understand project context:
+
+- `lspec stats` - See work distribution across specs
+- `lspec board` - View specs organized by status
+- `lspec list --tag=<tag>` - Find specs by tag (e.g., `--tag=api`)
+- `lspec search "<query>"` - Full-text search across specs
+- `lspec deps <spec>` - Check dependencies before starting work
+
+These commands help you understand what exists, what's in progress, and what depends on what.
+
+## Spec Frontmatter
+
+When creating or updating specs, include YAML frontmatter at the top:
+
+```yaml
+---
+status: draft|planned|in-progress|complete|blocked|cancelled
+created: YYYY-MM-DD
+tags: [tag1, tag2]  # helps with discovery
+priority: low|medium|high  # helps with planning
+assignee: username  # for team coordination
+---
+```
+
+**Core fields:**
+- `status` and `created` are required
+- `tags` help with discovery and organization
+- `priority` helps teams plan work
+- `assignee` shows who's working on what
+
+**Update status with:**
+```bash
+lspec update <spec> --status in-progress --assignee yourname
+# or edit frontmatter directly
+```
+
+## Workflow
+
+1. **Discover context** - Run `lspec stats` or `lspec board` to see current state
+2. **Search existing specs** - Use `lspec search` or `lspec list` to find relevant work
+3. **Check dependencies** - Run `lspec deps <spec>` if working on existing spec
+4. **Create or update spec** - Add frontmatter with required fields and helpful metadata
+5. **Implement changes** - Keep spec in sync as you learn
+6. **Update status** - Mark progress: `draft` → `in-progress` → `complete`
+7. **Archive when done** - `lspec archive <spec>` moves to archive
+
+## Quality Standards
+
+- Code is clear and maintainable
+- Tests cover critical paths
+- No unnecessary complexity
+- Documentation where needed (not everywhere)
+- Specs stay in sync with implementation
+
+---
+
+**Remember**: LeanSpec is a mindset. Adapt these guidelines to what actually helps.

package/templates/standard/spec-template.md

@@ -0,0 +1,35 @@
+---
+status: planned
+created: {date}
+tags: []
+priority: medium
+---
+
+# {name}
+
+> **Status**: 📅 Planned · **Priority**: Medium · **Created**: {date}
+
+## Overview
+
+<!-- What are we solving? Why now? -->
+
+## Design
+
+<!-- Technical approach, architecture decisions -->
+
+## Plan
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] Task 3
+
+## Test
+
+<!-- How will we verify this works? -->
+
+- [ ] Test criteria 1
+- [ ] Test criteria 2
+
+## Notes
+
+<!-- Optional: Research findings, alternatives considered, open questions -->