astragentic 1.5.0 → 2.0.0-y

package/CHANGELOG.md

@@ -0,0 +1,10 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [2.0.0-y] - 2026-01-05
+- using Kanban for tasks management
+
+## [1.0.0] - 2026-01-05
+- Initial release of Astragentic Installer.
+- Automated installation of .claude and _astraler.

package/README.md

@@ -49,9 +49,16 @@ When publishing manually from your local machine, **you do not need to manually
 
     The script will:
     - Update the version in `package.json`.
+    - **Prompt to update `CHANGELOG.md`** (optional).
     - Bundle the latest `devkit/claude-code` and `_astraler` content.
     - Ask for confirmation before running `npm publish`.
 
+    **Changelog & Non-interactive Mode:**
+    - To pass a changelog message automatically (e.g., in CI or fast mode):
+      ```bash
+      ./scripts/ship.sh 0.0.1 -y "Your changelog message here"
+      ```
+
 ### Automated Publishing (CI/CD)
 
 For CI/CD (like GitHub Actions), we use an automation token.

package/assets/_astraler/workflows/brownfield.md

@@ -305,7 +305,10 @@ Generate ALL of these in one pass:
 - Webhooks (if found)
 - Confidence markers for inferred sections
 
-#### `atlas/tasks.md`
+#### `atlas/6-backlog.md`
+- Phases overview (Documentation → Tech Debt → New Features)
+- Phase index table
+- Per-phase backlog items (BL-*)
 - Documentation completion tasks
 - Technical debt identified
 - Suggested improvements
@@ -392,8 +395,9 @@ Mark sections with confidence:
 | `atlas/screens.md` (per domain) | `02-spec/domains/{domain}.md` (screens) |
 | `atlas/api.md` (cross-domain) | `02-spec/core/flows.md` |
 | `atlas/api.md` (per domain) | `02-spec/domains/{domain}.md` (API) |
-| `atlas/tasks.md` | `04-tasks/milestones.md` |
-| `atlas/tasks.md` (per domain) | `04-tasks/domains/{domain}.tasks.md` |
+| `atlas/6-backlog.md` | `04-tasks/phases.md` |
+| `atlas/6-backlog.md` (milestones) | `04-tasks/milestones.md` |
+| `atlas/6-backlog.md` (per domain) | `04-tasks/domains/{domain}.tasks.md` (Kanban board) |
 | Scan results | `context/constraints.md` |
 | Clarification | `context/assumptions.md` |
 | Code analysis | `context/glossary.md` |
@@ -403,12 +407,13 @@ Mark sections with confidence:
 ```
 .astraler-docs/
 ├── _index.md
-├── atlas/                          # SOURCE (human-approved)
-│   ├── index.md
-│   ├── database.md
-│   ├── screens.md
-│   ├── api.md
-│   └── tasks.md
+├── atlas/                          # SOURCE (human-approved, read 1→6)
+│   ├── 1-overview.md
+│   ├── 2-context.md
+│   ├── 3-database.md
+│   ├── 4-screens.md
+│   ├── 5-api.md
+│   └── 6-backlog.md               # Phases + backlog items
 │
 ├── 02-spec/                        # AUTO-GENERATED from Atlas
 │   ├── _index.md
@@ -428,11 +433,12 @@ Mark sections with confidence:
 │   └── domains/
 │       └── {domain}.arch.md        # One per detected domain
 │
-├── 04-tasks/                       # AUTO-GENERATED from Atlas
+├── 04-tasks/                       # AUTO-GENERATED from Atlas (Kanban)
 │   ├── _index.md
-│   ├── milestones.md
+│   ├── phases.md                  # ← from atlas/6-backlog.md
+│   ├── milestones.md              # ← from atlas/6-backlog.md
 │   └── domains/
-│       └── {domain}.tasks.md       # One per detected domain
+│       └── {domain}.tasks.md       # Kanban board + tasks
 │
 ├── 05-changes/
 │   ├── _index.md
@@ -480,8 +486,10 @@ These sections need human validation:
 1. `03-arch/domains/payment.arch.md` — State machine inferred
 2. `02-spec/domains/order.md` — Business rules unclear
 
-### Ready to Build
-- Start with: `04-tasks/domains/{first-priority-domain}.tasks.md`
+### Ready to Build (Kanban Flow)
+- View phases: `04-tasks/phases.md` (PO visibility)
+- View board: `/astra:board {domain}` (dev visibility)
+- Pull next task: `/astra:board --next`
 - Validate: Low-confidence sections before implementation
 - Reference: `atlas/` for complete picture
 - Changes: Use `/astra:change` to modify approved docs
@@ -544,17 +552,20 @@ After expansion:
 - [ ] Business context provided
 - [ ] High-priority gaps resolved
 
-### Phase 3: Atlas Complete
-- [ ] `atlas/index.md` — All domains, tech stack
-- [ ] `atlas/database.md` — All entities, relationships
-- [ ] `atlas/screens.md` — All screens (if UI)
-- [ ] `atlas/api.md` — All endpoints
-- [ ] `atlas/tasks.md` — Documentation + improvement tasks
+### Phase 3: Atlas Complete (read in order)
+- [ ] `atlas/1-overview.md` — All domains, tech stack
+- [ ] `atlas/2-context.md` — Constraints, assumptions, glossary
+- [ ] `atlas/3-database.md` — All entities, relationships
+- [ ] `atlas/4-screens.md` — All screens (if UI)
+- [ ] `atlas/5-api.md` — All endpoints
+- [ ] `atlas/6-backlog.md` — Phases + backlog items
 
 ### Phase 4: Expansion Complete
 - [ ] `02-spec/` — Core + all domain specs
 - [ ] `03-arch/` — Overview + all domain arch
-- [ ] `04-tasks/` — Milestones + all domain tasks
+- [ ] `04-tasks/phases.md` — Phase definitions
+- [ ] `04-tasks/milestones.md` — Milestone tracking (no dates)
+- [ ] `04-tasks/domains/*.tasks.md` — Kanban boards per domain
 - [ ] `context/` — Constraints, assumptions, glossary
 - [ ] `ai/` — Guardrails, quality gates
 - [ ] All files have proper headers

package/assets/_astraler/workflows/greenfield.md

@@ -144,17 +144,18 @@ Validate complete understanding before generation:
 
 ### Atlas Folder Structure
 
-**Reading Order:** Files are numbered 1→5 for sequential reading.
+**Reading Order:** Files are numbered 1→6 for sequential reading.
 
 ```
 .astraler-docs/
 ├── _index.md
-├── atlas/                          # PRIMARY - read in order 1→5
+├── atlas/                          # PRIMARY - read in order 1→6
 │   ├── 1-overview.md              # High-level vision, goals, domains (start here)
 │   ├── 2-context.md               # Constraints, assumptions, glossary
 │   ├── 3-database.md              # Complete schema, ALL entities
 │   ├── 4-screens.md               # UI inventory (if UI exists)
-│   └── 5-api.md                   # API surface inventory (not detailed contracts)
+│   ├── 5-api.md                   # API surface inventory (not detailed contracts)
+│   └── 6-backlog.md               # Product backlog with Phases (PO visibility)
 ├── changes/
 │   ├── changelog.md
 │   └── impact/
@@ -203,6 +204,18 @@ Validate complete understanding before generation:
 
 **Simplicity:** Sketch the API surface only. No request/response schemas yet — those come during `/astra:plan` or implementation.
 
+#### `6-backlog.md` — Product Backlog with Phases
+- Phases overview diagram (Mermaid flowchart)
+- Phase index table (Phase, Goal, Milestones, Status)
+- Per-phase details:
+  - User value statement
+  - Included milestones
+  - High-level backlog items (BL-001, BL-002...)
+  - Phase acceptance criteria
+- Backlog prioritization guide (P0, P1, P2)
+
+**Purpose:** PO visibility into what each phase delivers. Backlog items (BL-*) expand into detailed tasks (TSK-*) during `/astra:plan`.
+
 ---
 
 ### Human Gate: Atlas Approval
@@ -212,12 +225,20 @@ After Atlas generation, present for review:
 ```markdown
 ## Atlas Complete
 
-### Generated Files (read in order 1→5)
+### Generated Files (read in order 1→6)
 - `atlas/1-overview.md` — {X} domains, tech stack, vision
 - `atlas/2-context.md` — constraints, assumptions, glossary
 - `atlas/3-database.md` — {Y} tables, {Z} relationships
 - `atlas/4-screens.md` — {W} screens across all domains
 - `atlas/5-api.md` — ~{V} endpoints (surface inventory)
+- `atlas/6-backlog.md` — {P} phases, {B} backlog items
+
+### Phases Defined
+| Phase | Goal | Milestones |
+|-------|------|------------|
+| Phase 1 | {user value} | M-01, M-02, ... |
+| Phase 2 | {user value} | M-03, M-04, ... |
+{ALL phases listed}
 
 ### Domains Covered
 | Domain | Priority | Entities | Screens | Endpoints |
@@ -230,7 +251,7 @@ Upon approval, will auto-generate:
 - 02-spec/core/* (3 files)
 - 02-spec/domains/* ({N} files)
 - 03-arch/* (3 files + {N} domain files)
-- 04-tasks/* (1 file + {N} domain files)
+- 04-tasks/* (phases.md + milestones.md + {N} domain files)
 
 ---
 **Approve Atlas?**
@@ -259,18 +280,22 @@ Upon approval, will auto-generate:
 | `atlas/5-api.md` (cross-domain) | `02-spec/core/flows.md` |
 | `atlas/5-api.md` (per domain) | `02-spec/domains/{domain}.md` (API section) |
 | `atlas/5-api.md` (per domain) | `03-arch/domains/{domain}.arch.md` (contracts) |
+| `atlas/6-backlog.md` | `04-tasks/phases.md` |
+| `atlas/6-backlog.md` (milestones) | `04-tasks/milestones.md` |
+| `atlas/6-backlog.md` (per domain) | `04-tasks/domains/{domain}.tasks.md` (Kanban board) |
 
 ### Generated Structure
 
 ```
 .astraler-docs/
 ├── _index.md
-├── atlas/                          # SOURCE (human-approved, read 1→5)
+├── atlas/                          # SOURCE (human-approved, read 1→6)
 │   ├── 1-overview.md
 │   ├── 2-context.md
 │   ├── 3-database.md
 │   ├── 4-screens.md
-│   └── 5-api.md
+│   ├── 5-api.md
+│   └── 6-backlog.md               # Phases + backlog items
 │
 ├── 02-spec/                        # AUTO-GENERATED from Atlas
 │   ├── _index.md
@@ -296,6 +321,16 @@ Upon approval, will auto-generate:
 │       ├── order.arch.md          # ← from atlas (order sections)
 │       └── ...                    # One per domain
 │
+├── 04-tasks/                       # AUTO-GENERATED from Atlas (Kanban)
+│   ├── _index.md
+│   ├── phases.md                  # ← from atlas/6-backlog.md
+│   ├── milestones.md              # ← from atlas/6-backlog.md
+│   └── domains/
+│       ├── auth.tasks.md          # Kanban board + tasks
+│       ├── catalog.tasks.md
+│       ├── order.tasks.md
+│       └── ...                    # One per domain
+│
 ├── 05-changes/
 │   ├── _index.md
 │   ├── changelog.md
@@ -322,16 +357,18 @@ Upon approval, will auto-generate:
 ### Files Generated
 | Folder | Files | From Atlas |
 |--------|-------|------------|
-| 02-spec/core/ | 3 | index.md, api.md |
+| 02-spec/core/ | 3 | 1-overview.md, 5-api.md |
 | 02-spec/domains/ | {N} | All atlas files |
-| 03-arch/ | 4 | index.md, database.md |
-| 03-arch/domains/ | {N} | database.md, api.md |
-| 04-tasks/ | 1 | tasks.md |
-| 04-tasks/domains/ | {N} | tasks.md |
+| 03-arch/ | 4 | 1-overview.md, 3-database.md |
+| 03-arch/domains/ | {N} | 3-database.md, 5-api.md |
+| 04-tasks/ | 2 | phases.md, milestones.md |
+| 04-tasks/domains/ | {N} | 6-backlog.md (Kanban boards) |
 | **Total** | **{total}** | |
 
-### Ready to Build
-- Start with: `04-tasks/domains/{first-priority-domain}.tasks.md`
+### Ready to Build (Kanban Flow)
+- View phases: `04-tasks/phases.md` (PO visibility)
+- View board: `/astra:board {domain}` (dev visibility)
+- Pull next task: `/astra:board --next`
 - Reference: `atlas/` for complete picture
 - Changes: Use `/astra:change` to modify approved docs
 ```
@@ -393,9 +430,13 @@ After expansion:
 - [ ] `atlas/3-database.md` — All entities, relationships
 - [ ] `atlas/4-screens.md` — All screens, navigation
 - [ ] `atlas/5-api.md` — API surface inventory (~count per domain)
+- [ ] `atlas/6-backlog.md` — Phases + backlog items (PO visibility)
 
 ### After Expansion
 - [ ] `02-spec/` — Core + all domain specs
 - [ ] `03-arch/` — Overview + all domain arch
+- [ ] `04-tasks/phases.md` — Phase definitions
+- [ ] `04-tasks/milestones.md` — Milestone tracking (no dates)
+- [ ] `04-tasks/domains/*.tasks.md` — Kanban boards per domain
 - [ ] All files have proper headers
 - [ ] All files have required diagrams

package/assets/claude-code/commands/astra/board.md

@@ -0,0 +1,176 @@
+---
+description: "Visualize and manage Kanban board"
+argument-hint: "[domain|all] [--move <task> <column>] [--prioritize <task> <P0|P1|P2>] [--next]"
+allowed-tools: ["Read", "Write", "Edit", "Glob"]
+---
+
+Kanban board visualization and task flow management.
+
+## Activation
+
+1. LOAD engine rules from `@_astraler/engine.md`
+2. Parse domain or subcommand from arguments
+3. Execute appropriate action
+
+## Subcommands
+
+### `/astra:board [domain]`
+
+Display current board state for a domain (or all domains):
+
+1. Read `.astraler-docs/04-tasks/domains/{domain}.tasks.md`
+2. Parse tasks by column (Backlog, Ready, In Progress, Review, Done)
+3. Display board visualization
+4. Highlight WIP violations (if In Progress > wip-limit)
+5. Show blocked tasks
+6. Display cycle time metrics
+
+**Output:**
+```
+## {Domain} Kanban Board
+
+| Backlog | Ready | In Progress (2/2) | Review | Done |
+|---------|-------|-------------------|--------|------|
+| TSK-004 | -     | TSK-002 P1        | -      | TSK-001 |
+| TSK-005 |       | TSK-003 P1        |        | TSK-008 |
+| ...     |       |                   |        |         |
+
+Metrics:
+- WIP: 2/2 (at limit)
+- Avg Cycle Time: 1.5 days
+- Throughput (7d): 2 tasks
+```
+
+### `/astra:board --move <task> <column>`
+
+Move a task to a new column:
+
+1. Validate task exists
+2. Validate column name (Backlog, Ready, In Progress, Review, Done)
+3. Check WIP limit for "In Progress" column
+4. Update task status in file
+5. Record timestamp for metrics (Entered Ready, Started, etc.)
+6. Update board visualization in file
+7. Display updated board
+
+**Columns:**
+| Column | Status Value | Timestamp Field |
+|--------|--------------|-----------------|
+| Backlog | Backlog | - |
+| Ready | Ready | Entered Ready |
+| In Progress | In Progress | Started |
+| Review | Review | - |
+| Done | Done | Completed |
+
+**WIP Enforcement:**
+- If moving to "In Progress" would exceed wip-limit, warn and ask for confirmation
+- Suggest which task to move out first
+
+### `/astra:board --prioritize <task> <priority>`
+
+Change task priority:
+
+1. Validate task exists
+2. Validate priority (P0, P1, P2, Backlog)
+3. Update priority field in task
+4. If P0 (Critical), highlight in output
+5. Reorder task in column by priority
+6. Display updated board
+
+**Priority Meanings:**
+| Priority | Label | Description |
+|----------|-------|-------------|
+| P0 | Critical | Blocking other work, immediate attention |
+| P1 | Current | Active focus, pull next |
+| P2 | Next | Coming soon, after P1 cleared |
+| Backlog | Future | Identified but not prioritized |
+
+### `/astra:board --next`
+
+Pull next task to work on:
+
+1. Find highest priority task in Ready column
+2. Check WIP limit
+3. If at limit, suggest completing or moving a task first
+4. If under limit, move task to In Progress
+5. Display task details for starting work
+
+**Output:**
+```
+## Next Task: TSK-order-004
+
+**Cancel order endpoint (DELETE /api/v1/orders/:id)**
+
+Priority: P2 → P1 (now active)
+Column: Ready → In Progress
+Dependencies: TSK-order-001 ✅, TSK-order-002 ✅
+
+Acceptance Criteria:
+- [ ] DELETE /api/v1/orders/:id endpoint
+- [ ] Authorization check (owner or seller or admin)
+- [ ] Return 200 with cancellation details
+...
+
+Ready to start? [y/n]
+```
+
+## Reads
+
+- `.astraler-docs/04-tasks/domains/{domain}.tasks.md`
+- `.astraler-docs/04-tasks/phases.md` (for phase context)
+- `.astraler-docs/04-tasks/milestones.md` (for milestone context)
+
+## Writes
+
+- `.astraler-docs/04-tasks/domains/{domain}.tasks.md` (when moving/prioritizing)
+
+## Board Visualization
+
+The board is stored as a Mermaid block-beta diagram in each tasks file:
+
+```mermaid
+block-beta
+    columns 5
+
+    block:backlog["Backlog"]
+        T004["TSK-004"]
+        T005["TSK-005"]
+    end
+
+    block:ready["Ready"]
+        space
+    end
+
+    block:doing["In Progress (2)"]
+        T002["TSK-002 P1"]
+        T003["TSK-003 P1"]
+    end
+
+    block:review["Review"]
+        space
+    end
+
+    block:done["Done"]
+        T001["TSK-001"]
+        T008["TSK-008"]
+    end
+```
+
+## Metrics Tracking
+
+Track in each task file:
+
+| Metric | Calculation |
+|--------|-------------|
+| WIP Current | Count of tasks in "In Progress" |
+| WIP Limit | From frontmatter `wip-limit` |
+| Avg Cycle Time | Avg (Completed - Entered Ready) for Done tasks |
+| Throughput | Count of tasks moved to Done in last 7 days |
+
+## Output
+
+After any board operation, display:
+1. Updated board visualization
+2. Current metrics
+3. WIP status (under/at/over limit)
+4. Next suggested action (if applicable)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "astragentic",
-  "version": "1.5.0",
+  "version": "2.0.0-y",
   "description": "Installer for Astragentic devkit",
   "bin": {
     "astragentic": "./bin/cli.js"