specdacular 0.7.1 → 0.8.0

package/specdacular/templates/features/DEPENDENCIES.md

@@ -1,47 +0,0 @@
-# Dependencies: {feature-name}
-
-**Last Updated:** {YYYY-MM-DD}
-
-## Overview
-
-{Brief description of how this feature spans multiple projects and what each project contributes.}
-
----
-
-## Project Involvement
-
-| Project | Role | Path |
-|---------|------|------|
-| {project-name} | {What this project does for this feature} | {./relative/path} |
-
----
-
-## Phase Dependencies
-
-| Phase | Depends On | Status |
-|-------|------------|--------|
-| {project}/phase-{N} | — | pending |
-| {project}/phase-{N} | {project}/phase-{N} | blocked |
-
-**Status values:** `pending` | `blocked` | `in-progress` | `complete`
-
----
-
-## Dependency Graph
-
-```mermaid
-graph TD
-    A1[{project-a}/phase-1] --> A2[{project-a}/phase-2]
-    B1[{project-b}/phase-1] --> B2[{project-b}/phase-2]
-    A2 --> B2
-```
-
----
-
-## Scheduling Notes
-
-{Notes about execution order, parallelism opportunities, and constraints.}
-
-- Phases with no dependencies can start immediately
-- Phases with all dependencies `complete` are unblocked
-- The `next` command reads this table to determine what work is available

package/specdacular/templates/features/PLAN.md

@@ -1,180 +0,0 @@
----
-feature: {feature-name}
-phase: {N}
-plan: {NN}
-depends_on: []
-creates:
-  - {path/to/new/file.ts}
-  - {path/to/new/file.tsx}
-modifies:
-  - {path/to/existing/file.ts}
----
-
-# Plan {NN}: {Plan Title}
-
-## Objective
-
-{What this plan accomplishes and why. 1-2 sentences max.}
-
-## Context
-
-**Reference these files:**
-- `@.specd/codebase/PATTERNS.md` — Code patterns to follow
-- `@.specd/codebase/STRUCTURE.md` — Where files go
-- `@{path/to/pattern/file}` — Pattern to follow for this task
-
-**Relevant Decisions:**
-- DEC-XXX: {Decision that affects this plan}
-- DEC-YYY: {Another relevant decision}
-
-**From Research:** (if RESEARCH.md exists)
-- {Key finding that affects implementation}
-- {Pitfall to avoid}
-
----
-
-## Tasks
-
-### Task 1: {Task Title}
-
-**Files:** `{path/to/file}`
-
-**Action:**
-{Clear description of what to create or modify. Include enough detail that the implementing agent doesn't need to ask questions.}
-
-Follow pattern from `{path/to/example}`:
-```{language}
-// Pattern to follow
-{code example showing the pattern}
-```
-
-Create:
-```{language}
-// What to create
-{code example or structure}
-```
-
-**Verify:**
-```bash
-{command to verify task is complete}
-```
-
-**Done when:**
-- [ ] {Specific, observable completion criterion}
-- [ ] {Another criterion}
-
----
-
-### Task 2: {Task Title}
-
-**Files:** `{path/to/file}`
-
-**Action:**
-{Clear description}
-
-**Pattern:**
-```{language}
-{code pattern}
-```
-
-**Verify:**
-```bash
-{verification command}
-```
-
-**Done when:**
-- [ ] {Completion criterion}
-
----
-
-### Task 3: {Task Title}
-
-**Files:** `{path/to/file}`
-
-**Action:**
-{Clear description}
-
-**Verify:**
-```bash
-{verification command}
-```
-
-**Done when:**
-- [ ] {Completion criterion}
-
----
-
-## Verification
-
-After all tasks complete, verify the plan is done:
-
-```bash
-# Type check (if TypeScript)
-npx tsc --noEmit
-
-# Run tests (if applicable)
-npm test -- --grep "{relevant tests}"
-
-# Manual verification
-{any manual checks needed}
-```
-
-**Plan is complete when:**
-- [ ] All tasks marked done
-- [ ] All verification commands pass
-- [ ] No TypeScript errors
-- [ ] {Any plan-specific criteria}
-
----
-
-## Output
-
-When this plan is complete:
-
-1. Update `.specd/features/{feature-name}/STATE.md`:
-   - Mark this plan as complete
-   - Note any discoveries or decisions made
-
-2. Commit changes:
-   ```bash
-   git add {files created/modified}
-   git commit -m "feat({feature}): {what was accomplished}
-
-   Plan {phase}.{plan} complete:
-   - {summary of what was done}"
-   ```
-
-3. Next plan: `phase-{NN}/{NN+1}-PLAN.md` (if exists)
-
----
-
-## Implementation Log
-
-During implementation, capture decisions and deviations to `.specd/features/{feature-name}/CHANGELOG.md`.
-
-**When to log:**
-- Choosing a different approach than specified
-- Adding functionality not in the plan
-- Skipping or modifying a task
-- Discovering issues that change the approach
-
-**Format:**
-```markdown
-### {YYYY-MM-DD} - Plan {NN}
-
-**{Brief title}**
-- **What:** {What you decided/changed}
-- **Why:** {Reason for the change}
-- **Files:** `{affected files}`
-```
-
-**Don't log:**
-- Minor implementation details
-- Standard coding patterns
-- Things working as planned
-
----
-
-## Notes
-
-{Space for the implementing agent to record discoveries, blockers, or decisions made during implementation. Leave empty in template.}

package/specdacular/templates/features/RESEARCH.md

@@ -1,183 +0,0 @@
-# Research: {feature-name}
-
-**Researched:** {YYYY-MM-DD}
-**Feature type:** {what kind of feature}
-**Confidence:** {HIGH/MEDIUM/LOW}
-
-## Summary
-
-{2-3 paragraphs synthesizing all research findings}
-
-- What's the recommended approach?
-- What makes this feature fit well with the existing codebase?
-- What are the key risks and how to mitigate them?
-
-**Key recommendation:** {One-liner actionable guidance for the planner}
-
----
-
-## Codebase Integration
-
-How this feature fits with existing code.
-
-### Import Dependencies
-
-| Module | Provides | Path |
-|--------|----------|------|
-| {module} | {what it provides} | `{path}` |
-
-### Patterns to Follow
-
-**{Pattern name}**
-Follow pattern in `{existing file path}`:
-- {Key aspect 1}
-- {Key aspect 2}
-
-```typescript
-// Example from {path}
-{code snippet showing pattern}
-```
-
-### File Structure
-
-Where new files should go:
-
-```
-src/
-├── {path}/           # {purpose}
-│   ├── {file}.ts     # {what it does}
-│   └── {file}.tsx    # {what it does}
-└── {existing}/       # Modify: {what change}
-```
-
-### Reusable Code
-
-**Types:**
-- `@{path}` — {what types}
-
-**Utilities:**
-- `@{path}` — {what utilities}
-
-**Components:**
-- `@{path}` — {what components}
-
-### Integration Points
-
-| Connect To | Via | Purpose |
-|------------|-----|---------|
-| {system} | {how} | {why} |
-
----
-
-## Implementation Approach
-
-Standard patterns and libraries for this feature type.
-
-### Standard Stack
-
-| Library | Version | Purpose | Confidence |
-|---------|---------|---------|------------|
-| {lib} | {ver}+ | {purpose} | {HIGH/MEDIUM} |
-
-### Architecture Pattern
-
-**Pattern:** {name}
-**Why:** {rationale for this codebase}
-
-```
-{diagram or structure}
-```
-
-### Code Patterns
-
-**{Pattern name}**
-```typescript
-// Source: {Context7 library ID / docs URL}
-{verified code example}
-```
-
-**{Pattern name}**
-```typescript
-// Source: {Context7 library ID / docs URL}
-{verified code example}
-```
-
-### Don't Hand-Roll
-
-| Problem | Use Instead | Why |
-|---------|-------------|-----|
-| {problem} | {library/utility} | {edge cases it handles} |
-
----
-
-## Pitfalls
-
-What commonly goes wrong and how to prevent it.
-
-### Critical
-
-**{Pitfall name}**
-- What goes wrong: {description}
-- Why it happens: {root cause}
-- Prevention: {specific steps}
-- Detection: {warning signs during implementation}
-
-### Moderate
-
-**{Pitfall name}**
-- What goes wrong: {description}
-- Prevention: {specific steps}
-
-### Task-Specific Warnings
-
-| When Implementing | Watch Out For | Prevention |
-|-------------------|---------------|------------|
-| {task/file} | {pitfall} | {how to avoid} |
-
----
-
-## Confidence Assessment
-
-| Area | Level | Reason |
-|------|-------|--------|
-| Codebase integration | {level} | {why - e.g., "patterns clear from existing code"} |
-| Implementation approach | {level} | {why - e.g., "verified with Context7"} |
-| Pitfalls | {level} | {why - e.g., "multiple sources agree"} |
-
----
-
-## Open Questions
-
-Things that couldn't be fully resolved during research:
-
-1. **{Question}**
-   - What we know: {partial info}
-   - What's unclear: {the gap}
-   - Recommendation: {how planner should handle}
-
----
-
-## Sources
-
-### Codebase (from Explore)
-- `{path}` — {what was learned}
-
-### Verified External (HIGH confidence)
-- Context7: {library IDs and queries}
-- Official docs: {URLs}
-
-### Community (MEDIUM confidence)
-- {Verified WebSearch findings with URLs}
-
-### For Awareness Only (LOW confidence)
-- {Unverified findings - not used in recommendations}
-
----
-
-## Decisions Made
-
-Decisions recorded in DECISIONS.md during this research:
-
-| Decision | Rationale |
-|----------|-----------|
-| DEC-XXX: {title} | {brief rationale} |

package/specdacular/templates/features/STATE.md

@@ -1,110 +0,0 @@
-# State: {feature-name}
-
-## Current Position
-
-**Stage:** {discussion | research | planning | execution}
-**Last Updated:** {YYYY-MM-DD}
-
----
-
-## Stage Progress
-
-### Discussion
-- [x] Initial discussion complete
-- [ ] Gray areas identified
-- [ ] All gray areas resolved
-
-### Research
-- [ ] Research conducted
-- [ ] Findings documented in RESEARCH.md
-
-### Planning
-- [ ] Phases derived
-- [ ] Plans created
-
-### Execution
-- [ ] Phase 1 complete
-- [ ] Phase 2 complete
-
----
-
-## Execution Progress
-
-### Phase Status
-
-Phase status tracks: `pending` → `executing` → `executed` → `completed`
-- **pending** — Phase not yet started (prepare/plan needed)
-- **executing** — Plans are being executed
-- **executed** — All plans done, pending user review
-- **completed** — User approved, ready for next phase
-
-Current phase status is tracked in `config.json` → `phases.current_status`.
-
-### Current Plan
-- Plan: none
-- Task: —
-- Started: —
-
-### Completed Plans
-| Plan | Completed | Tasks | Deviations |
-|------|-----------|-------|------------|
-
----
-
-## Review Cycles
-
-| Phase | Cycle | Date | Findings | Corrective Plans | Status |
-|-------|-------|------|----------|------------------|--------|
-
----
-
-## Discussion Sessions
-
-| Date | Focus | Outcome |
-|------|-------|---------|
-| {YYYY-MM-DD} | Initial discussion | FEATURE.md created |
-
----
-
-## Documents Status
-
-| Document | Status | Last Updated |
-|----------|--------|--------------|
-| FEATURE.md | Created | {date} |
-| CONTEXT.md | Created | {date} |
-| DECISIONS.md | {N} decisions | {date} |
-| RESEARCH.md | Not started | — |
-| ROADMAP.md | Not started | — |
-| plans/ | Not started | — |
-
----
-
-## Decision Count
-
-- **Active:** {N}
-- **Superseded:** {N}
-- **Total:** {N}
-
----
-
-## Next Steps
-
-{What the user should do next based on current state.}
-
-**Resume:** `/specd:feature:continue {feature-name}` — Picks up where you left off and guides the next step automatically.
-
----
-
-## Session Notes
-
-{Space for notes during sessions. Cleared or archived as appropriate.}
-
----
-
-## Quick Reference
-
-- **Feature:** `.specd/features/{feature-name}/FEATURE.md`
-- **Context:** `.specd/features/{feature-name}/CONTEXT.md`
-- **Decisions:** `.specd/features/{feature-name}/DECISIONS.md`
-- **Research:** `.specd/features/{feature-name}/RESEARCH.md`
-- **Roadmap:** `.specd/features/{feature-name}/ROADMAP.md`

package/specdacular/templates/features/config.json

@@ -1,20 +0,0 @@
-{
-  "feature_name": "{name}",
-  "feature_abbrev": "{ABBREV}",
-  "created": "{date}",
-  "mode": "interactive",
-  "depth": "standard",
-  "phases": {
-    "total": 0,
-    "completed": 0,
-    "current": 1
-  },
-  "requirements": {
-    "v1_count": 0,
-    "v2_count": 0,
-    "completed": 0
-  },
-  "execution": {
-    "auto_commit": false
-  }
-}