prizmkit 1.0.99 → 1.0.101

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.99",
-  "bundledAt": "2026-03-23T13:30:18.410Z",
-  "bundledFrom": "df41166"
+  "frameworkVersion": "1.0.101",
+  "bundledAt": "2026-03-23T16:44:31.127Z",
+  "bundledFrom": "7da7d80"
 }

package/bundled/dev-pipeline/launch-daemon.sh

@@ -93,6 +93,7 @@ cmd_start() {
     local feature_list=""
     local env_overrides=""
     local mode_override=""
+    local features_filter=""
 
     # Parse arguments
     while [[ $# -gt 0 ]]; do
@@ -123,6 +124,15 @@ cmd_start() {
                 esac
                 shift
                 ;;
+            --features)
+                shift
+                if [[ $# -eq 0 ]]; then
+                    log_error "--features requires a value (e.g. --features F-001,F-003 or --features F-001:F-010)"
+                    exit 1
+                fi
+                features_filter="$1"
+                shift
+                ;;
             *)
                 feature_list="$1"
                 shift
@@ -199,6 +209,9 @@ cmd_start() {
     log_info "Launching pipeline..."
     log_info "Feature list: $feature_list"
     log_info "Log file: $LOG_FILE"
+    if [[ -n "$features_filter" ]]; then
+        log_info "Features filter: $features_filter"
+    fi
     if [[ -n "$mode_override" ]]; then
         log_info "Mode: $mode_override"
     fi
@@ -212,6 +225,9 @@ cmd_start() {
         echo "================================================================"
         echo "  Pipeline Daemon Started: $start_time"
         echo "  Feature list: $feature_list"
+        if [[ -n "$features_filter" ]]; then
+            echo "  Features filter: $features_filter"
+        fi
         if [[ -n "$mode_override" ]]; then
             echo "  Mode: $mode_override"
         fi
@@ -227,11 +243,17 @@ cmd_start() {
     # is inherited and blocks child claude processes with "nested sessions" error.
     unset CLAUDECODE 2>/dev/null || true
 
+    # Build features flag
+    local features_flag=""
+    if [[ -n "$features_filter" ]]; then
+        features_flag="--features $features_filter"
+    fi
+
     # Launch with nohup + disown for full detachment
     if [[ -n "$env_cmd" ]]; then
-        nohup $env_cmd "$RUN_SCRIPT" run "$feature_list" >> "$LOG_FILE" 2>&1 &
+        nohup $env_cmd "$RUN_SCRIPT" run "$feature_list" $features_flag >> "$LOG_FILE" 2>&1 &
     else
-        nohup "$RUN_SCRIPT" run "$feature_list" >> "$LOG_FILE" 2>&1 &
+        nohup "$RUN_SCRIPT" run "$feature_list" $features_flag >> "$LOG_FILE" 2>&1 &
     fi
     local pipeline_pid=$!
     disown "$pipeline_pid" 2>/dev/null || true
@@ -548,20 +570,23 @@ show_help() {
 Usage: launch-daemon.sh <command> [options]
 
 Commands:
-  start [feature-list.json] [--mode <mode>] [--env "K=V ..."]   Start pipeline in background
+  start [feature-list.json] [--mode <mode>] [--features <filter>] [--env "K=V ..."]   Start pipeline in background
   stop                                            Gracefully stop pipeline
   status                                          Check if pipeline is running
   logs [--lines N] [--follow]                     View pipeline logs
-  restart [feature-list.json] [--mode <mode>] [--env "K=V ..."]  Stop + start pipeline
+  restart [feature-list.json] [--mode <mode>] [--features <filter>] [--env "K=V ..."]  Stop + start pipeline
   help                                            Show this help
 
 Options:
   --mode <lite|standard|full|self-evolve>   Override pipeline mode for all features
+  --features <filter>                       Run only specified features (e.g. F-001,F-003 or F-001:F-010)
   --env "KEY=VAL ..."                        Set environment variables
 
 Examples:
   ./launch-daemon.sh start                        # Start with default feature-list.json
   ./launch-daemon.sh start my-features.json       # Start with custom feature list
+  ./launch-daemon.sh start --features F-001:F-005  # Run only features F-001 through F-005
+  ./launch-daemon.sh start --features F-001,F-003,F-007  # Run specific features
   ./launch-daemon.sh start --mode self-evolve     # Self-evolve mode (framework development)
   ./launch-daemon.sh start --env "MAX_RETRIES=5 SESSION_TIMEOUT=7200"
   ./launch-daemon.sh start feature-list.json --mode self-evolve --env "VERBOSE=1"

package/bundled/dev-pipeline/run.sh

@@ -783,6 +783,7 @@ print(data.get('reload_needed', False))
 
 main() {
     local feature_list="${1:-feature-list.json}"
+    local features_filter="${2:-}"
 
     # Resolve to absolute path
     if [[ ! "$feature_list" = /* ]]; then
@@ -842,6 +843,9 @@ main() {
     echo -e "${BOLD}          Dev-Pipeline Runner Started${NC}"
     echo -e "${BOLD}════════════════════════════════════════════════════${NC}"
     log_info "Feature list: $feature_list"
+    if [[ -n "$features_filter" ]]; then
+        log_info "Features filter: $features_filter"
+    fi
     log_info "Max retries per feature: $MAX_RETRIES"
     if [[ $SESSION_TIMEOUT -gt 0 ]]; then
         log_info "Session timeout: ${SESSION_TIMEOUT}s"
@@ -889,11 +893,17 @@ for f in data.get('stuck_features', []):
 
         # Find next feature to process
         local next_feature
+        local _get_next_args=(
+            --feature-list "$feature_list"
+            --state-dir "$STATE_DIR"
+            --max-retries "$MAX_RETRIES"
+            --action get_next
+        )
+        if [[ -n "$features_filter" ]]; then
+            _get_next_args+=(--features "$features_filter")
+        fi
         next_feature=$(python3 "$SCRIPTS_DIR/update-feature-status.py" \
-            --feature-list "$feature_list" \
-            --state-dir "$STATE_DIR" \
-            --max-retries "$MAX_RETRIES" \
-            --action get_next 2>/dev/null) || true
+            "${_get_next_args[@]}" 2>/dev/null) || true
 
         if [[ "$next_feature" == "PIPELINE_COMPLETE" ]]; then
             echo ""
@@ -1060,13 +1070,18 @@ show_help() {
     echo "Usage: $0 <command> [options]"
     echo ""
     echo "Commands:"
-    echo "  run [feature-list.json]                 Run all features sequentially"
+    echo "  run [feature-list.json] [--features <filter>]  Run features (all or filtered subset)"
     echo "  run <feature-id> [options]              Run a single feature"
     echo "  status [feature-list.json]               Show pipeline status"
     echo "  test-cli                                 Test AI CLI: show detected CLI, version, and model"
     echo "  reset                                    Clear all state and start fresh"
     echo "  help                                     Show this help message"
     echo ""
+    echo "Feature Filter (--features):"
+    echo "  --features F-001,F-003,F-005             Run only specified features"
+    echo "  --features F-001:F-010                   Run a range of features (F-001 through F-010)"
+    echo "  --features F-001,F-005:F-010             Mixed: individual IDs + ranges"
+    echo ""
     echo "Single Feature Options (run <feature-id>):"
     echo "  --dry-run                   Generate bootstrap prompt only, don't spawn session"
     echo "  --resume-phase N            Override resume phase (default: auto-detect)"
@@ -1089,6 +1104,8 @@ show_help() {
     echo ""
     echo "Examples:"
     echo "  ./run.sh run                                         # Run all features"
+    echo "  ./run.sh run --features F-001,F-003,F-005             # Run specific features"
+    echo "  ./run.sh run --features F-001:F-010                   # Run features F-001 through F-010"
     echo "  ./run.sh run F-007 --dry-run                          # Inspect generated prompt"
     echo "  ./run.sh run F-007 --dry-run --mode lite               # Test lite mode"
     echo "  ./run.sh run F-007 --resume-phase 6                    # Skip to implementation"
@@ -1107,7 +1124,27 @@ case "${1:-run}" in
         if [[ "${1:-}" =~ ^[Ff]-[0-9]+ ]]; then
             run_one "$@"
         else
-            main "${1:-feature-list.json}"
+            # Parse positional and --features flag
+            local _run_feature_list="feature-list.json"
+            local _run_features_filter=""
+            while [[ $# -gt 0 ]]; do
+                case "$1" in
+                    --features)
+                        shift
+                        if [[ $# -eq 0 ]]; then
+                            log_error "--features requires a value (e.g. --features F-001,F-003 or --features F-001:F-010)"
+                            exit 1
+                        fi
+                        _run_features_filter="$1"
+                        shift
+                        ;;
+                    *)
+                        _run_feature_list="$1"
+                        shift
+                        ;;
+                esac
+            done
+            main "$_run_feature_list" "$_run_features_filter"
         fi
         ;;
     status)

package/bundled/dev-pipeline/scripts/update-feature-status.py

@@ -16,7 +16,8 @@ Usage:
         --feature-list <path> --state-dir <path> \
         --action <get_next|start|update|status|pause|reset|clean|complete> \
         [--feature-id <id>] [--session-status <status>] \
-        [--session-id <id>] [--max-retries <n>]
+        [--session-id <id>] [--max-retries <n>] \
+        [--features <filter>]
 """
 
 import argparse
@@ -102,9 +103,49 @@ def parse_args():
         default=None,
         help="Project root directory. Required for 'clean' action.",
     )
+    parser.add_argument(
+        "--features",
+        default=None,
+        help="Feature filter: comma-separated IDs (F-001,F-003) or range (F-001:F-010), or mixed.",
+    )
     return parser.parse_args()
 
 
+def parse_feature_filter(features_str):
+    """Parse --features argument into a set of feature IDs.
+
+    Supported formats:
+      F-001,F-003,F-005   -> {"F-001", "F-003", "F-005"}
+      F-001:F-010          -> {"F-001", "F-002", ..., "F-010"}
+      F-001,F-005:F-010    -> mixed, union of both
+
+    Returns None if features_str is None/empty (meaning no filter).
+    """
+    if not features_str:
+        return None
+
+    result = set()
+    for part in features_str.split(","):
+        part = part.strip()
+        if not part:
+            continue
+        if ":" in part:
+            tokens = part.split(":", 1)
+            m_start = re.search(r"\d+", tokens[0])
+            m_end = re.search(r"\d+", tokens[1])
+            if not m_start or not m_end:
+                error_out("Invalid range format: {}".format(part))
+            start_num = int(m_start.group())
+            end_num = int(m_end.group())
+            if start_num > end_num:
+                start_num, end_num = end_num, start_num
+            for i in range(start_num, end_num + 1):
+                result.add("F-{:03d}".format(i))
+        else:
+            result.add(part.upper())
+    return result if result else None
+
+
 def now_iso():
     """Return the current UTC time in ISO8601 format."""
     return datetime.now(timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ")
@@ -285,20 +326,31 @@ def load_session_status(state_dir, feature_id, session_id):
 # Action: get_next
 # ---------------------------------------------------------------------------
 
-def action_get_next(feature_list_data, state_dir):
+def action_get_next(feature_list_data, state_dir, feature_filter=None):
     """Find the next feature to process.
 
     Priority logic:
     1. Skip terminal statuses (completed, failed, skipped)
-    2. Check that all dependencies are completed
-    3. Prefer in_progress features over pending ones (interrupted session resume)
-    4. Among eligible features, pick lowest priority number (highest priority)
+    2. If feature_filter is set, skip features not in the filter
+    3. Check that all dependencies are completed
+    4. Prefer in_progress features over pending ones (interrupted session resume)
+    5. Among eligible features, pick lowest priority number (highest priority)
     """
     features = feature_list_data.get("features", [])
     if not features:
         print("PIPELINE_COMPLETE")
         return
 
+    # Apply feature filter: only consider features in the whitelist
+    if feature_filter is not None:
+        features = [
+            f for f in features
+            if isinstance(f, dict) and f.get("id") in feature_filter
+        ]
+        if not features:
+            print("PIPELINE_COMPLETE")
+            return
+
     # Build a map of feature statuses from state dir
     status_map = {}  # feature_id -> status string
     status_data_map = {}  # feature_id -> full status data
@@ -678,7 +730,7 @@ def _estimate_remaining_time(features, state_dir, counts, feature_list_data=None
     return remaining_seconds, confidence
 
 
-def action_status(feature_list_data, state_dir):
+def action_status(feature_list_data, state_dir, feature_filter=None):
     """Print a formatted overview of all features and their status.
 
     Status is read exclusively from feature-list.json (the single source of
@@ -688,6 +740,13 @@ def action_status(feature_list_data, state_dir):
     features = feature_list_data.get("features", [])
     app_name = feature_list_data.get("app_name", "Unknown")
 
+    # Apply feature filter
+    if feature_filter is not None:
+        features = [
+            f for f in features
+            if isinstance(f, dict) and f.get("id") in feature_filter
+        ]
+
     # Gather status info
     counts = {
         "completed": 0,
@@ -1080,15 +1139,18 @@ def main():
     if err:
         error_out("Cannot load feature list: {}".format(err))
 
+    # Parse feature filter (used by get_next and status)
+    feature_filter = parse_feature_filter(args.features)
+
     # Dispatch action
     if args.action == "get_next":
-        action_get_next(feature_list_data, args.state_dir)
+        action_get_next(feature_list_data, args.state_dir, feature_filter)
     elif args.action == "start":
         action_start(args, args.feature_list, args.state_dir)
     elif args.action == "update":
         action_update(args, args.feature_list, args.state_dir)
     elif args.action == "status":
-        action_status(feature_list_data, args.state_dir)
+        action_status(feature_list_data, args.state_dir, feature_filter)
     elif args.action == "reset":
         action_reset(args, args.feature_list, args.state_dir)
     elif args.action == "clean":

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.99",
+  "version": "1.0.101",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

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

@@ -28,6 +28,7 @@ Use daemon mode (`launch-daemon.sh`) only when:
 - "launch pipeline", "start implementing", "run the pipeline", "start auto-development"
 - "implement next steps", "execute feature list", "start building"
 - After app-planner completes: "build it", "start developing from the feature list"
+- "run only F-001 to F-005", "run features F-001,F-003", "only build these features"
 
 **Check status** -- User says:
 - "pipeline status", "check pipeline", "how's it going", "progress"
@@ -117,11 +118,20 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```bash
    dev-pipeline/run.sh run feature-list.json
    ```
+   If user wants to run only specific features:
+   ```bash
+   dev-pipeline/run.sh run feature-list.json --features F-001:F-005
+   dev-pipeline/run.sh run feature-list.json --features F-001,F-003,F-007
+   ```
 
    **If option 2 (background)**:
    ```bash
    dev-pipeline/launch-daemon.sh start feature-list.json
    ```
+   With feature filter:
+   ```bash
+   dev-pipeline/launch-daemon.sh start feature-list.json --features F-001:F-005
+   ```
    Note: Pipeline runs fully detached. Survives session closure.
 
    **If option 3 (manual)**: Print commands and stop. Do not execute anything.
@@ -251,7 +261,35 @@ dev-pipeline/launch-daemon.sh start feature-list.json --env "SESSION_TIMEOUT=720
 
 ---
 
-#### Intent F: Retry Single Feature Node
+#### Intent F: Run Subset of Features
+
+When user says "run only F-001 to F-005", "only build features 1 through 5":
+
+```bash
+dev-pipeline/run.sh run feature-list.json --features F-001:F-005
+```
+
+When user says "run F-001, F-003, and F-007", "only build these three features":
+
+```bash
+dev-pipeline/run.sh run feature-list.json --features F-001,F-003,F-007
+```
+
+Mixed format (IDs + ranges):
+
+```bash
+dev-pipeline/run.sh run feature-list.json --features F-001,F-005:F-010
+```
+
+Background daemon with feature filter:
+
+```bash
+dev-pipeline/launch-daemon.sh start feature-list.json --features F-001:F-005
+```
+
+---
+
+#### Intent G: Retry Single Feature Node
 
 When user says "retry F-003":
 

package/bundled/skills/prizmkit-init/SKILL.md

@@ -43,10 +43,10 @@ BROWNFIELD WORKFLOW (existing project):
 **Step 1: Project Scanning**
 1. Detect tech stack from build files (`package.json`, `requirements.txt`, `go.mod`, `pom.xml`, `Cargo.toml`, etc.)
 2. Map directory structure using a TWO-TIER model — flat structures lose the nesting relationships that AI needs to navigate the codebase:
-   - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `dev-pipeline/`, `src/`, `internal/`)
-   - SUB-MODULES: directories INSIDE a top-level module (e.g. `dev-pipeline/scripts/`, `dev-pipeline/lib/`)
+   - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `src/`, `internal/`, `lib/`)
+   - SUB-MODULES: directories INSIDE a top-level module (e.g. `src/routes/`, `src/models/`)
    - A sub-module maps to `.prizm-docs/<M>/<S>.prizm`, never to `.prizm-docs/<S>.prizm` — flattening would create ambiguous paths when two modules have identically-named sub-modules
-   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`
+   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`, `dev-pipeline/`
 3. Identify entry points by language convention
 4. Catalog dependencies (external packages)
 5. Count source files per directory

package/bundled/skills/prizmkit-prizm-docs/SKILL.md

@@ -48,7 +48,7 @@ STEPS:
    - TOP-LEVEL modules: directories directly under project root (or under src/ for src-based layouts) that contain 3+ source files OR contain sub-directories with 3+ source files. These go into MODULE_INDEX.
    - SUB-MODULES: directories INSIDE a top-level module that contain 3+ source files. Listed in the parent L1 doc's SUBDIRS section only.
    - HIERARCHY RULE: directory X inside top-level module M maps to .prizm-docs/<M>/<X>.prizm, never to .prizm-docs/<X>.prizm.
-   - Exclude vendor/, node_modules/, .git/, build/, dist/, __pycache__/, target/, bin/. If top-level module count > 30, ask user for include/exclude patterns.
+   - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/. If top-level module count > 30, ask user for include/exclude patterns.
 3. Create .prizm-docs/ directory structure mirroring the source tree exactly. For each top-level module M that has sub-modules, create the subdirectory .prizm-docs/<M>/.
 4. Generate root.prizm (L0) with PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, MODULE_INDEX listing only top-level modules with arrow pointers to .prizm-docs/<M>.prizm (sub-modules stay out of MODULE_INDEX to keep L0 compact and within the 4KB limit), RULES extracted from CODEBUDDY.md/CLAUDE.md/README/linter configs, and PATTERNS. Set PRIZM_VERSION: 2, UPDATED: today's date. Max 4KB.
 5. Generate L1 .prizm files for ALL modules (top-level and sub-modules), each at its correct mirrored path:

package/bundled/skills/prizmkit-prizm-docs/assets/PRIZM-SPEC.md

@@ -479,19 +479,19 @@ STEPS:
    a. IDENTIFY TOP-LEVEL modules: directories directly under project root (or directly under src/ for src-based layouts) that either:
       - Contain 3+ source files of the primary language, OR
       - Contain sub-directories that each have 3+ source files
-      RESULT: top_modules = [dev-pipeline, src, internal, app, ...]
+      RESULT: top_modules = [src, internal, app, lib, ...]
 
    b. IDENTIFY SUB-MODULES: for each top-level module M, find directories INSIDE M that contain 3+ source files
       RESULT: sub_modules[M] = [scripts, lib, templates, ...]  (relative names, not full paths)
 
    c. HIERARCHY RULE: if directory X lives inside top-level module M, X is a sub-module of M — NOT a separate top-level module.
-      WRONG: dev-pipeline/scripts/ treated as top-level module -> .prizm-docs/scripts.prizm
-      CORRECT: dev-pipeline/scripts/ is a sub-module of dev-pipeline -> .prizm-docs/dev-pipeline/scripts.prizm
+      WRONG: src/routes/ treated as top-level module -> .prizm-docs/routes.prizm
+      CORRECT: src/routes/ is a sub-module of src -> .prizm-docs/src/routes.prizm
 
    d. MODULE_INDEX in root.prizm lists ONLY top-level modules from step 2a.
       Sub-modules appear in their parent's L1 doc SUBDIRS section, not in MODULE_INDEX.
 
-   - EXCLUDE: vendor/, node_modules/, .git/, build/, dist/, __pycache__/, target/, bin/
+   - EXCLUDE: .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/
    IF top-level module count > 30: ASK user for include/exclude patterns
 
 3. CREATE_DIRECTORY_STRUCTURE:
@@ -499,10 +499,10 @@ STEPS:
    For each top-level module M that has sub-modules: create .prizm-docs/<M>/ directory
    RULE: .prizm-docs/ directory tree must mirror the source directory tree exactly
    EXAMPLE:
-     source: dev-pipeline/scripts/  -> prizm: .prizm-docs/dev-pipeline/scripts.prizm
-     source: dev-pipeline/lib/      -> prizm: .prizm-docs/dev-pipeline/lib.prizm
-     source: dev-pipeline/          -> prizm: .prizm-docs/dev-pipeline.prizm
-   NEVER create .prizm-docs/scripts.prizm for a directory that lives at dev-pipeline/scripts/
+     source: src/routes/     -> prizm: .prizm-docs/src/routes.prizm
+     source: src/models/     -> prizm: .prizm-docs/src/models.prizm
+     source: src/            -> prizm: .prizm-docs/src.prizm
+   NEVER create .prizm-docs/routes.prizm for a directory that lives at src/routes/
 
 4. GENERATE_ROOT (L0):
    Fill: PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY from step 1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.99",
+  "version": "1.0.101",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {