prizmkit 1.1.6 → 1.1.8

package/bundled/skills/feature-pipeline-launcher/SKILL.md

@@ -49,7 +49,7 @@ Three execution modes are available. The user chooses one before configuring oth
 Before any action, validate:
 
 1. **dev-pipeline exists**: Confirm `dev-pipeline/launch-feature-daemon.sh` is present and executable
-2. **For start**: `feature-list.json` must exist in project root (or user-specified path)
+2. **For start**: `.prizmkit/plans/feature-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
 3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
 4. **Python version**: Requires Python 3.8+ for dev-pipeline scripts
 5. **playwright-cli** (optional): If any feature has `browser_interaction` field, check `playwright-cli` is available
@@ -61,8 +61,8 @@ command -v jq && command -v python3 && (command -v cbc || command -v claude) &&
 command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (browser verification will be skipped)"
 ```
 
-If `feature-list.json` is missing, inform user:
-> "No feature-list.json found. Run the `feature-planner` skill first to generate one, or provide a path to your feature list."
+If `.prizmkit/plans/feature-list.json` is missing, inform user:
+> "No .prizmkit/plans/feature-list.json found. Run the `feature-planner` skill first to generate one, or provide a path to your feature list."
 
 ### Workflow
 
@@ -74,7 +74,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check prerequisites**:
    ```bash
-   ls feature-list.json 2>/dev/null && echo "Found" || echo "Missing"
+   ls .prizmkit/plans/feature-list.json 2>/dev/null && echo "Found" || echo "Missing"
    ```
 
 2. **Check not already running**:
@@ -87,7 +87,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```bash
    python3 -c "
    import json
-   with open('feature-list.json') as f:
+   with open('.prizmkit/plans/feature-list.json') as f:
        data = json.load(f)
    features = data.get('features', [])
    print(f'Total features: {len(features)}')
@@ -98,8 +98,8 @@ Detect user intent from their message, then follow the corresponding workflow:
    If pipeline state already exists, use the status command instead:
    ```bash
    python3 dev-pipeline/scripts/update-feature-status.py \
-     --feature-list feature-list.json \
-     --state-dir dev-pipeline/state \
+     --feature-list .prizmkit/plans/feature-list.json \
+     --state-dir .prizmkit/state/features \
      --action status 2>/dev/null
    ```
 
@@ -107,11 +107,11 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    Run the preflight script to auto-detect the database type, verify env vars, test connectivity, and check migration status:
    ```bash
-   python3 ${SKILL_DIR}/scripts/preflight-check.py feature-list.json
+   python3 ${SKILL_DIR}/scripts/preflight-check.py .prizmkit/plans/feature-list.json
    ```
 
    The script:
-   - Reads `global_context.database` from `feature-list.json` and `.prizmkit/config.json`
+   - Reads `global_context.database` from `.prizmkit/plans/feature-list.json` and `.prizmkit/config.json`
    - Scans `.env.local` / `.env` for connection variables (supports Supabase, PostgreSQL, MySQL, MongoDB, Firebase, and generic `DATABASE_URL`)
    - Tests connectivity using the appropriate method per database type
    - Checks migration status (Prisma, Drizzle, Supabase raw SQL, or generic migration directories)
@@ -176,34 +176,34 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Foreground command:**
    ```bash
-   VERBOSE=1 dev-pipeline/run-feature.sh run feature-list.json
+   VERBOSE=1 dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
    ```
    With all options:
    ```bash
    VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 SESSION_TIMEOUT=3600 \
-     dev-pipeline/run-feature.sh run feature-list.json --features F-001:F-005
+     dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 
    **Background daemon command:**
    ```bash
-   dev-pipeline/launch-feature-daemon.sh start feature-list.json --env "VERBOSE=1"
+   dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --env "VERBOSE=1"
    ```
    With all options:
    ```bash
-   dev-pipeline/launch-feature-daemon.sh start feature-list.json --features F-001:F-005 \
+   dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --features F-001:F-005 \
      --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.
    ```
    # To run in foreground:
-   VERBOSE=1 dev-pipeline/run-feature.sh run feature-list.json
+   VERBOSE=1 dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 
    # To run in background (detached):
-   dev-pipeline/launch-feature-daemon.sh start feature-list.json --env "VERBOSE=1"
+   dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --env "VERBOSE=1"
 
    # To check status:
-   dev-pipeline/run-feature.sh status feature-list.json
+   dev-pipeline/run-feature.sh status .prizmkit/plans/feature-list.json
    ```
 
 8. **Confirm and launch** (Foreground and Background only — Manual mode ends at step 7):
@@ -227,7 +227,7 @@ Detect user intent from their message, then follow the corresponding workflow:
       ```
    2. Start log monitoring — Use the Bash tool with `run_in_background: true`:
       ```bash
-      tail -f dev-pipeline/state/pipeline-daemon.log
+      tail -f .prizmkit/state/features/pipeline-daemon.log
       ```
    3. Report to user:
       - Pipeline PID
@@ -247,14 +247,14 @@ Detect user intent from their message, then follow the corresponding workflow:
 2. **Show feature-level progress**:
    ```bash
    python3 dev-pipeline/scripts/update-feature-status.py \
-     --feature-list feature-list.json \
-     --state-dir dev-pipeline/state \
+     --feature-list .prizmkit/plans/feature-list.json \
+     --state-dir .prizmkit/state/features \
      --action status
    ```
 
 3. **Show recent log activity** (last 20 lines):
    ```bash
-   tail -20 dev-pipeline/state/pipeline-daemon.log
+   tail -20 .prizmkit/state/features/pipeline-daemon.log
    ```
 
 4. **Summarize** to user: total features, completed, in-progress, failed, pending.
@@ -286,20 +286,20 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
    ```bash
-   tail -f dev-pipeline/state/pipeline-daemon.log
+   tail -f .prizmkit/state/features/pipeline-daemon.log
    ```
 
 3. **If not running** -- Show last 50 lines:
    ```bash
-   tail -50 dev-pipeline/state/pipeline-daemon.log
+   tail -50 .prizmkit/state/features/pipeline-daemon.log
    ```
 
 4. **For per-feature session logs** (when user asks about a specific feature):
    ```bash
    # Check feature status for last session ID
-   cat dev-pipeline/state/features/<FEATURE_ID>/status.json 2>/dev/null
+   cat .prizmkit/state/features/features/<FEATURE_ID>/status.json 2>/dev/null
    # Then tail that feature's session log
-   tail -100 dev-pipeline/state/features/<FEATURE_ID>/sessions/<SESSION_ID>/logs/session.log
+   tail -100 .prizmkit/state/features/features/<FEATURE_ID>/sessions/<SESSION_ID>/logs/session.log
    ```
 
 ---
@@ -309,18 +309,18 @@ Detect user intent from their message, then follow the corresponding workflow:
 When user says "retry F-003":
 
 ```bash
-dev-pipeline/retry-feature.sh F-003 feature-list.json
+dev-pipeline/retry-feature.sh F-003 .prizmkit/plans/feature-list.json
 ```
 
 When user says "clean retry F-003" or "retry F-003 from scratch":
 
 ```bash
-dev-pipeline/reset-feature.sh F-003 --clean --run feature-list.json
+dev-pipeline/reset-feature.sh F-003 --clean --run .prizmkit/plans/feature-list.json
 ```
 
 Environment variables (optional):
 ```bash
-SESSION_TIMEOUT=3600 dev-pipeline/retry-feature.sh F-003 feature-list.json
+SESSION_TIMEOUT=3600 dev-pipeline/retry-feature.sh F-003 .prizmkit/plans/feature-list.json
 ```
 
 Notes:
@@ -339,7 +339,7 @@ After pipeline completion, if features have `browser_interaction` fields and `pl
    ```bash
    python3 -c "
    import json
-   with open('feature-list.json') as f:
+   with open('.prizmkit/plans/feature-list.json') as f:
        data = json.load(f)
    for feat in data.get('features', []):
        bi = feat.get('browser_interaction')
@@ -368,14 +368,14 @@ After pipeline completion, if features have `browser_interaction` fields and `pl
 
 | Error | Action |
 |-------|--------|
-| `feature-list.json` not found | Tell user to run `feature-planner` skill first |
+| `.prizmkit/plans/feature-list.json` not found | Tell user to run `feature-planner` skill first |
 | `jq` not installed | Suggest: `brew install jq` |
 | `cbc`/`claude` not in PATH | Check AI CLI installation |
 | Pipeline already running | Show status, ask if user wants to stop and restart |
 | PID file stale (process dead) | `launch-feature-daemon.sh` auto-cleans, retry start |
-| Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 dev-pipeline/state/pipeline-daemon.log` |
+| Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/features/pipeline-daemon.log` |
 | Feature stuck/blocked | Use `retry-feature.sh <F-XXX>` to retry; use `reset-feature.sh <F-XXX> --clean --run` for fresh start |
-| All features blocked/failed | Show status, suggest daemon-safe recovery: `dev-pipeline/reset-feature.sh <F-XXX> --clean --run feature-list.json` |
+| All features blocked/failed | Show status, suggest daemon-safe recovery: `dev-pipeline/reset-feature.sh <F-XXX> --clean --run .prizmkit/plans/feature-list.json` |
 | `playwright-cli` not installed | Browser verification skipped (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
 | Permission denied on script | Run `chmod +x dev-pipeline/launch-feature-daemon.sh dev-pipeline/run-feature.sh` |
 | Pipeline stop failed (process won't die) | Process may be stuck in I/O wait. Try `kill -9 <PID>` manually. Check for orphaned child processes with `ps aux \| grep claude` |
@@ -385,9 +385,9 @@ After pipeline completion, if features have `browser_interaction` fields and `pl
 
 ### Integration Notes
 
-- **After feature-planner**: This is the natural next step. When user finishes planning and has `feature-list.json`, suggest launching the pipeline.
+- **After feature-planner**: This is the natural next step. When user finishes planning and has `.prizmkit/plans/feature-list.json`, suggest launching the pipeline.
 - **Session independence**: The pipeline runs completely detached. User can close the AI CLI session, open a new session later, and use this skill to check progress or stop the pipeline.
 - **Single instance**: Only one pipeline can run at a time. The PID file prevents duplicates.
-- **Pipeline coexistence**: Feature and bugfix pipelines use separate state directories (`state/` vs `bugfix-state/`), so they can run simultaneously without conflict.
+- **Pipeline coexistence**: Feature and bugfix pipelines use separate state directories (`.prizmkit/state/features/` vs `.prizmkit/state/bugfix/`), so they can run simultaneously without conflict.
 - **State preservation**: Stopping and restarting the pipeline resumes from where it left off -- completed features are not re-run.
 - **HANDOFF**: After pipeline completes all features, each session has already run `prizmkit-retrospective` internally. Ask user what's next.

package/bundled/skills/feature-pipeline-launcher/scripts/preflight-check.py

@@ -2,11 +2,11 @@
 """
 dev-pipeline environment preflight checker.
 
-Detects database type from feature-list.json / .prizmkit/config.json,
+Detects database type from .prizmkit/plans/feature-list.json / .prizmkit/config.json,
 verifies env vars, tests connectivity, and checks migration status.
 
 Usage:
-    python3 preflight-check.py [feature-list.json]
+    python3 preflight-check.py [.prizmkit/plans/feature-list.json]
 
 Output: PREFLIGHT lines to stdout (✓ / ⚠ / ℹ), JSON summary to stderr.
 Exit code: 0 = all clear, 1 = warnings found, 2 = error.
@@ -402,7 +402,7 @@ def check_dev_server(feature_list_path):
 # ── Main ────────────────────────────────────────────────────────
 
 def main():
-    feature_list = sys.argv[1] if len(sys.argv) > 1 else "feature-list.json"
+    feature_list = sys.argv[1] if len(sys.argv) > 1 else ".prizmkit/plans/feature-list.json"
 
     if not os.path.isfile(feature_list):
         print(f"PREFLIGHT ⚠ Feature list not found: {feature_list}")

package/bundled/skills/feature-planner/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: "feature-planner"
-description: "Plan and manage features for an existing project — add new features, reprioritize, split, and generate validated feature-list.json for dev-pipeline execution. Use this skill for feature scoping, incremental planning, continuing a feature plan, or preparing pipeline input. For planning a new app from scratch, use app-planner instead."
+description: "Plan and manage features for an existing project — add new features, reprioritize, split, and generate validated .prizmkit/plans/feature-list.json for dev-pipeline execution. Use this skill for feature scoping, incremental planning, continuing a feature plan, or preparing pipeline input. For planning a new app from scratch, use app-planner instead."
 ---
 
 # feature planner
 
 Plan deliverable features for dev-pipeline on existing projects:
-- **New Feature Set**: create an initial feature-list.json for a project that has code but no plan yet
+- **New Feature Set**: create an initial .prizmkit/plans/feature-list.json for a project that has code but no plan yet
 - **Incremental Feature Planning**: append, adjust, or reprioritize features in an existing plan
 
-Always produce a validated `feature-list.json` that conforms to `dev-pipeline-feature-list`.
+Always produce a validated `.prizmkit/plans/feature-list.json` that conforms to `dev-pipeline-feature-list`.
 
 For planning a **new application from scratch** (vision, tech stack, decomposition), use `app-planner` instead.
 
@@ -35,24 +35,24 @@ The user chose this skill intentionally. Respect that choice.
 - Create, modify, or delete source code files (*.js, *.ts, *.py, *.go, *.html, *.css, etc.)
 - Create project scaffolding, directories, or boilerplate
 - Run build/install/test commands (npm init, pip install, etc.)
-- Execute any implementation action beyond writing `feature-list.json`
+- Execute any implementation action beyond writing `.prizmkit/plans/feature-list.json`
 
 **Your ONLY writable outputs are:**
-1. `feature-list.json` (project root)
+1. `.prizmkit/plans/feature-list.json` (`.prizmkit/plans/`)
 2. Draft backups in `.prizmkit/planning/`
 
 **After planning is complete**, you MUST:
 1. Present the summary and recommended next step
 2. **Ask the user explicitly** whether they want to proceed to execution
 3. If the user agrees → recommend invoking `feature-pipeline-launcher` or running `run-feature.sh` (do NOT execute it yourself)
-4. If the user wants to adjust → continue refining `feature-list.json`
+4. If the user wants to adjust → continue refining `.prizmkit/plans/feature-list.json`
 5. **NEVER auto-execute** the pipeline, launcher, or any implementation step
 
 ## When to Use
 
 Trigger this skill for requests like:
 - "Add features to existing system", "Continue planning"
-- "Prepare feature-list.json", "Prepare dev-pipeline input"
+- "Prepare .prizmkit/plans/feature-list.json", "Prepare dev-pipeline input"
 - "Reprioritize features", "Split features"
 - "Plan features for my project" (when the project already exists)
 
@@ -79,43 +79,115 @@ Do NOT use this skill when:
    ```bash
    python3 ${SKILL_DIR}/scripts/validate-and-generate.py validate --input <output-path> --mode <new|incremental>
    ```
+   
+   If the script is not available, perform these manual validation checks:
+   1. **ID sequence**: All feature IDs are sequential (F-001, F-002, F-003, ...)
+   2. **No circular dependencies**: No feature depends (directly or transitively) on itself
+   3. **Description length**: Minimum 15 words per description (error), 30/50/80 recommended
+   4. **Dependency references**: All referenced features in dependencies exist in features array
+   5. **Priority enums**: All priority values are exactly "high", "medium", or "low" (case-sensitive)
+   6. **Status enum**: All status values are one of: pending, in_progress, completed, failed, skipped, split, auto_skipped
+   7. **Acceptance criteria**: At least 1 criterion per feature, each is a concrete, measurable statement
+   8. **Browser interaction**: If present, has url, verify_steps array, and optional setup_command
+   9. **Complexity enum**: If present, is one of: low, medium, high
+   10. **Model field**: If present, is a non-empty string
+   11. **Critic field**: If present, is boolean; if true, critic_count should be 1 or 3
+   12. **Root schema**: Has $schema='dev-pipeline-feature-list-v1', project_name, and non-empty features array
 
 5. **Use script output as source of truth** — if validation fails, fix and re-run until pass
 
 ## Prerequisites
 
 Before questions, check optional context files (never block if absent):
-- `.prizm-docs/root.prizm` (architecture/project context)
+- `.prizm-docs/root.prizm` (architecture/project context — typically created by app-planner with captured decisions)
 - `.prizmkit/config.json` (existing stack preferences and detected tech stack)
-- existing `feature-list.json` (required for incremental mode)
+- `.prizmkit/plans/project-brief.md` (project context from app-planner, if available)
+- existing `.prizmkit/plans/feature-list.json` (required for incremental mode)
+- `.prizmkit/project-conventions.json` (project conventions from app-planner, if available)
 - If `.prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure to understand the codebase layout:
   ```bash
   find . -maxdepth 2 -type d -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/__pycache__/*' -not -path '*/vendor/*' | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
   ```
 
 **Tech stack from config.json:**
-- If `.prizmkit/config.json` contains a `tech_stack` object, use it to pre-fill `global_context` fields in the generated `feature-list.json`.
+- If `.prizmkit/config.json` contains a `tech_stack` object, use it to pre-fill `global_context` fields in the generated `.prizmkit/plans/feature-list.json`.
 - Map config fields to global_context: `language`, `runtime`, `frontend_framework`, `frontend_styling`, `backend_framework`, `database`, `orm`, `testing` → `testing_strategy`, `bundler`, `project_type`.
 - Do NOT re-ask the user for tech stack info already present in config.json. Show detected stack and confirm.
 
+## Global Context Population
+
+The `global_context` object in `.prizmkit/plans/feature-list.json` provides technology stack information to the pipeline for intelligent code generation.
+
+### Recommended Fields by Project Type
+
+**Frontend-only projects:**
+- `language` (required) — e.g., "TypeScript", "JavaScript"
+- `frontend_framework` (required) — e.g., "React", "Vue", "Svelte"
+- `frontend_styling` (recommended) — e.g., "Tailwind CSS", "styled-components"
+- `testing_strategy` (recommended) — e.g., "Jest + React Testing Library"
+
+**Backend-only projects:**
+- `language` (required) — e.g., "TypeScript", "Python", "Go"
+- `backend_framework` (required) — e.g., "Express", "Django", "FastAPI"
+- `database` (required if applicable) — e.g., "PostgreSQL", "MongoDB"
+- `testing_strategy` (recommended) — e.g., "Jest", "pytest"
+
+**Full-stack projects (include both frontend AND backend fields):**
+- `language`, `frontend_framework`, `backend_framework`, `database`, `testing_strategy` (all recommended)
+- Additional: `frontend_styling`, `orm`, `bundler`, `runtime`
+
+### Auto-Population from app-planner
+
+If the project was planned with `app-planner`, `feature-planner` will automatically read:
+- `.prizmkit/config.json` (tech stack detected by app-planner)
+- `.prizmkit/plans/project-brief.md` (tech choices made during planning)
+- `.prizm-docs/root.prizm` (architecture decisions)
+
+**Recommendation**: Always run `app-planner` before `feature-planner` to ensure `global_context` is pre-populated correctly. This reduces planning time and improves code generation consistency.
+
+### Manual Population (if no app-planner context)
+
+If planning features directly without app-planner:
+1. During Phase 1 (Scope Clarification), identify the project's tech stack
+2. Ask user or read from existing `package.json` / `pyproject.toml` / `go.mod`
+3. Populate `global_context` in `.prizmkit/plans/feature-list.json` with detected values
+4. Confirm with user: "Using tech stack: [language] + [frameworks]. Correct?"
+
+### Pipeline Behavior with Missing Fields
+
+| Missing Field | Pipeline Behavior |
+|---------------|-------------------|
+| `language` | Uses generic pseudocode patterns; code generation may be generic |
+| `frontend_framework` | Frontend features generate generic HTML/JavaScript; no framework-specific patterns |
+| `backend_framework` | Backend features generate generic API patterns; no framework-specific scaffolding |
+| `database` | Assumes no persistent storage; generates unit tests only with mocks |
+| `testing_strategy` | Defaults to Jest (if JavaScript/TypeScript); pytest (if Python) |
+| All fields empty | Pipeline still works but code quality/consistency may suffer; recommend re-running with app-planner |
+
+### Note
+
+**global_context fields are all optional** — pipeline can execute without them. However, including the recommended fields dramatically improves code generation quality and framework-specific best practices.
+
+---
+
 ## Scenario Routing
 
 Classify user intent first:
 
 ### Route A: New Feature Set (No Existing Plan)
-Use when the project exists but has no `feature-list.json` yet.
+Use when the project exists but has no `.prizmkit/plans/feature-list.json` yet.
 
 Actions:
 1. Understand the existing codebase and what's already implemented
 2. Run interactive planning phases to identify needed features
-3. Generate initial `feature-list.json`
+3. Generate initial `.prizmkit/plans/feature-list.json`
 
 ### Route B: Incremental Feature Planning
-Use when user already has a `feature-list.json` and wants to add or adjust features.
+Use when user already has a `.prizmkit/plans/feature-list.json` and wants to add or adjust features.
 
 Actions:
 1. Load `${SKILL_DIR}/references/incremental-feature-planning.md`
-2. Read existing `feature-list.json` first (if missing, ask whether to start new plan)
+2. Read existing `.prizmkit/plans/feature-list.json` first (if missing, ask whether to start new plan)
 3. Append features with next sequential `F-NNN` IDs
 4. Preserve style/language/detail consistency with existing plan
 
@@ -133,7 +205,7 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
    4.2 **Browser interaction** (mandatory for fullstack/frontend projects) — see §Browser Interaction Planning below. Qualifying features get `browser_interaction` by default. Only confirm with the user as a batch summary; do NOT ask per-feature.
 5. Verify DAG/order/priorities
 6. Pre-generation completeness review (see §Pre-Generation Completeness Review below)
-7. Build or append `feature-list.json`
+7. Build or append `.prizmkit/plans/feature-list.json`
 8. Apply default testing strategy (see §Testing Defaults below)
 9. Validate and fix until pass
 10. Summarize final feature table
@@ -150,14 +222,14 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 | **CP-FP-3.1** | Browser Interaction Applied | Qualifying features have `browser_interaction` field; user confirmed or opted out | 4 |
 | **CP-FP-3.2** | Testing Defaults Applied | All features have appropriate `critic`, `critic_count`, and testing expectations | 7 |
 | **CP-FP-3.3** | Completeness Review Passed | All features reviewed for description adequacy and cross-feature gaps | 6 |
-| **CP-FP-4** | `feature-list.json` Generated | Schema validates, all required keys present | 7-8 |
+| **CP-FP-4** | `.prizmkit/plans/feature-list.json` Generated | Schema validates, all required keys present | 7-8 |
 | **CP-FP-5** | Final Validation Pass | Python script returns `"valid": true` with zero errors | 9 |
 
 **Resume Detection**: If existing artifacts are found, read `${SKILL_DIR}/references/error-recovery.md` §Resume Support for checkpoint-based resumption.
 
 ## Pre-Generation Completeness Review (Phase 6)
 
-Before generating `feature-list.json`, review the full feature set holistically. Individual features may look fine in isolation but have gaps when viewed together.
+Before generating `.prizmkit/plans/feature-list.json`, review the full feature set holistically. Individual features may look fine in isolation but have gaps when viewed together.
 
 ### Step 1: Description Adequacy Scan
 
@@ -211,7 +283,7 @@ For simple incremental planning, skip detailed Phase 2-3 analysis:
 - **No architectural changes** to existing tech stack
 
 ### Fast Path Workflow
-1. Read existing `feature-list.json` and confirm scope
+1. Read existing `.prizmkit/plans/feature-list.json` and confirm scope
 2. **User confirmation (mandatory)** — Tell the user: "This qualifies for fast-path (simple incremental addition). Skip detailed Phase 2-3 analysis and draft directly? Or use full workflow?" Only proceed with fast path if user confirms.
 3. Generate next sequential feature IDs
 4. Draft features (title + description + acceptance_criteria + dependencies)
@@ -242,7 +314,7 @@ A feature is **exempt** when ANY true:
 
 ## Output Rules
 
-`feature-list.json` must satisfy:
+`.prizmkit/plans/feature-list.json` must satisfy:
 - `$schema` = `dev-pipeline-feature-list-v1`
 - non-empty `features`
 - sequential feature IDs (`F-001`, `F-002`, ...)
@@ -291,7 +363,7 @@ Recommend these three options in this strict order:
 1. **Preferred**: invoke `feature-pipeline-launcher` skill
 2. **Fallback A**: run daemon wrapper
    ```bash
-   ./dev-pipeline/launch-feature-daemon.sh start feature-list.json
+   ./dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json
    ./dev-pipeline/launch-feature-daemon.sh status
    ```
 3. **Fallback B**: run direct foreground script
@@ -308,7 +380,7 @@ Key behaviors:
 - Warnings only → proceed with user approval
 - Critical errors → group by type, auto-fix where possible, max 3 total attempts
 - Interrupted session → detect checkpoint from existing artifacts, offer resume or restart
-- `feature-list.json` MUST be written to project root (same level as `package.json` / `.git`)
+- `.prizmkit/plans/feature-list.json` MUST be written to `.prizmkit/plans/` (project root level: `./{root}/.prizmkit/plans/feature-list.json`)
 
 ## Session Exit Gate
 
@@ -316,13 +388,13 @@ Prevent accidental session exit without deliverable completion.
 
 ### Trigger Conditions
 Activate when ALL true:
-- User expressed intent to produce feature-list.json
+- User expressed intent to produce .prizmkit/plans/feature-list.json
 - Current phase < Phase 7
-- No valid `feature-list.json` written in this session
+- No valid `.prizmkit/plans/feature-list.json` written in this session
 
 ### Gate Behavior
 When the session appears to be ending:
-1. **Remind**: "You set out to produce `feature-list.json` but we haven't completed it yet."
+1. **Remind**: "You set out to produce `.prizmkit/plans/feature-list.json` but we haven't completed it yet."
 2. **Offer 3 options**:
    - **(a) Continue to completion**
    - **(b) Save draft & exit** — write current progress as draft

package/bundled/skills/feature-planner/references/error-recovery.md

@@ -21,7 +21,7 @@ Group errors by type and apply targeted fixes:
 
 | Error Type | Symptom | Fix Offered | Auto-Fix? |
 |-----------|---------|------------|-----------|
-| **Schema mismatch** | `$schema` invalid, missing `app_name`, wrong `features` type | "Set `$schema` to `dev-pipeline-feature-list-v1`, `app_name` to string" | Yes |
+| **Schema mismatch** | `$schema` invalid, missing `project_name`, wrong `features` type | "Set `$schema` to `dev-pipeline-feature-list-v1`, `project_name` to string" | Yes |
 | **Feature ID issues** | Invalid format (not `F-NNN`), duplicate IDs, undefined refs | "Suggest corrected IDs, show duplicates" | Yes |
 | **Dependency errors** | Circular dependency, undefined target features | "Show cycle chain (e.g., `F-003 → F-005 → F-003`), suggest break point" | No |
 | **Missing fields** | Feature missing required keys (title, description, AC) | "List each feature + missing keys, guide patch" | Partial |
@@ -90,20 +90,20 @@ If in Incremental mode but existing `feature-list.json` not found:
 
 ### Artifact Path Convention
 
-**CRITICAL PATH RULE**: `feature-list.json` MUST be written to the project root directory
-(same level as `package.json` / `.git`).
+**CRITICAL PATH RULE**: `feature-list.json` MUST be written to `.prizmkit/plans/` directory
+(unified artifact location).
 
-Before writing, verify: `ls package.json .git 2>/dev/null` — if these exist in the current
-directory, you are at the project root. NEVER write to `dev-pipeline/` or any subdirectory.
+Before writing, verify: `ls .prizmkit 2>/dev/null` — if this directory exists in the current
+directory, you are at the project root. If not, create `.prizmkit/plans/` first (mkdir -p .prizmkit/plans).
 
-After writing, verify: `ls -la feature-list.json` from project root.
+After writing, verify: `ls -la .prizmkit/plans/feature-list.json` from project root.
 
 ```
 <project-root>/
-  ├── feature-list.json              # Primary output (always here, at project root)
-  └── .prizmkit/planning/            # Optional organization for backups
+  └── .prizmkit/plans/
+      ├── feature-list.json              # Primary output (always here, at .prizmkit/plans/)
       ├── feature-list.validated.json    # Checkpoint backup after CP-FP-5
       └── <ISO-timestamp>.backup.json    # Optional incremental backups
 ```
 
-The pipeline reads `feature-list.json` from the project root by default. If the user specifies a custom path, the launcher accepts it as an argument.
+The pipeline reads `feature-list.json` from `.prizmkit/plans/` by default. If the user specifies a custom path, the launcher accepts it as an argument.

package/bundled/skills/feature-planner/scripts/validate-and-generate.py

@@ -4,15 +4,15 @@ validate-and-generate.py - Validate and generate feature-list.json files
 for the dev-pipeline system.
 
 Commands:
-  validate    Validate an existing feature-list.json
-  template    Generate a blank template feature-list.json
-  summary     Print a summary table of features from a feature-list.json
+  validate    Validate an existing .prizmkit/plans/feature-list.json
+  template    Generate a blank template .prizmkit/plans/feature-list.json
+  summary     Print a summary table of features from a .prizmkit/plans/feature-list.json
   grade       Generate grading results from eval runs (for npm run skill:review)
 
 Usage:
-  python3 validate-and-generate.py validate --input feature-list.json [--output validated.json] [--mode new|incremental]
-  python3 validate-and-generate.py template --output feature-list.json
-  python3 validate-and-generate.py summary --input feature-list.json [--format markdown|json]
+  python3 validate-and-generate.py validate --input .prizmkit/plans/feature-list.json [--output validated.json] [--mode new|incremental]
+  python3 validate-and-generate.py template --output .prizmkit/plans/feature-list.json
+  python3 validate-and-generate.py summary --input .prizmkit/plans/feature-list.json [--format markdown|json]
   python3 validate-and-generate.py grade --workspace /.codebuddy/skill-evals/feature-planner-workspace --iteration iteration-1
 
 Python 3.6+ required. No external dependencies.
@@ -174,9 +174,10 @@ def validate_feature_list(data, planning_mode="new"):
             "$schema must be '{}', got '{}'".format(SCHEMA_VERSION, schema)
         )
 
-    app_name = data.get("app_name")
+    # Support both project_name (canonical) and app_name (legacy)
+    app_name = data.get("project_name", data.get("app_name"))
     if not isinstance(app_name, str) or not app_name.strip():
-        errors.append("app_name must be a non-empty string")
+        errors.append("project_name must be a non-empty string")
 
     features = data.get("features")
     if not isinstance(features, list) or len(features) == 0:
@@ -441,8 +442,8 @@ def generate_template():
 
     return {
         "$schema": SCHEMA_VERSION,
-        "app_name": "YOUR_APP_NAME",
-        "app_description": "YOUR_APP_DESCRIPTION",
+        "project_name": "YOUR_PROJECT_NAME",
+        "project_description": "YOUR_PROJECT_DESCRIPTION",
         "created_at": now,
         "created_by": "feature-planner",
         "source_spec": "",
@@ -545,7 +546,7 @@ def _build_dependency_graph_text(features):
 
 def generate_summary_markdown(data):
     """Generate a markdown summary of the feature list."""
-    app_name = data.get("app_name", "Unknown")
+    app_name = data.get("project_name", data.get("app_name", "Unknown"))
     features = data.get("features", [])
 
     lines = []
@@ -634,7 +635,7 @@ def generate_summary_json(data):
         })
 
     return {
-        "app_name": data.get("app_name", ""),
+        "project_name": data.get("project_name", data.get("app_name", "")),
         "features": feature_summaries,
         "stats": {
             "total_features": len(features),
@@ -846,16 +847,16 @@ def cmd_grade(args):
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Validate and generate feature-list.json files for the dev-pipeline system.",
+        description="Validate and generate .prizmkit/plans/feature-list.json files for the dev-pipeline system.",
         formatter_class=argparse.RawDescriptionHelpFormatter,
         epilog=(
             "Examples:\n"
-            "  %(prog)s validate --input feature-list.json\n"
-            "  %(prog)s validate --input feature-list.json --mode incremental\n"
-            "  %(prog)s validate --input feature-list.json --output validated.json\n"
-            "  %(prog)s template --output feature-list.json\n"
-            "  %(prog)s summary --input feature-list.json\n"
-            "  %(prog)s summary --input feature-list.json --format json\n"
+            "  %(prog)s validate --input .prizmkit/plans/feature-list.json\n"
+            "  %(prog)s validate --input .prizmkit/plans/feature-list.json --mode incremental\n"
+            "  %(prog)s validate --input .prizmkit/plans/feature-list.json --output validated.json\n"
+            "  %(prog)s template --output .prizmkit/plans/feature-list.json\n"
+            "  %(prog)s summary --input .prizmkit/plans/feature-list.json\n"
+            "  %(prog)s summary --input .prizmkit/plans/feature-list.json --format json\n"
         ),
     )
 
@@ -864,10 +865,10 @@ def main():
     # -- validate --
     p_validate = subparsers.add_parser(
         "validate",
-        help="Validate an existing feature-list.json",
+        help="Validate an existing .prizmkit/plans/feature-list.json",
     )
     p_validate.add_argument(
-        "--input", required=True, help="Path to input feature-list.json"
+        "--input", required=True, help="Path to input .prizmkit/plans/feature-list.json"
     )
     p_validate.add_argument(
         "--output", help="Path to write validated output (optional)"
@@ -882,7 +883,7 @@ def main():
     # -- template --
     p_template = subparsers.add_parser(
         "template",
-        help="Generate a blank template feature-list.json",
+        help="Generate a blank template .prizmkit/plans/feature-list.json",
     )
     p_template.add_argument(
         "--output", required=True, help="Path to write template file"
@@ -891,10 +892,10 @@ def main():
     # -- summary --
     p_summary = subparsers.add_parser(
         "summary",
-        help="Print a summary table of features from a feature-list.json",
+        help="Print a summary table of features from a .prizmkit/plans/feature-list.json",
     )
     p_summary.add_argument(
-        "--input", required=True, help="Path to input feature-list.json"
+        "--input", required=True, help="Path to input .prizmkit/plans/feature-list.json"
     )
     p_summary.add_argument(
         "--format",