ai-core-framework 0.1.0 → 0.3.0

package/{core/scripts → scripts}/validate-permissions.sh

@@ -25,7 +25,21 @@ command_file_for() {
   local command="$1"
   local name
   name=$(printf '%s' "$command" | sed 's#^/##')
-  find core/commands -name "$name.md" -type f | head -1
+
+  if [ -d "commands" ]; then
+    find commands -name "$name.md" -type f | head -1
+    return 0
+  fi
+
+  if [ -d "skills" ]; then
+    find skills -name 'SKILL.md' -type f -print0 |
+      while IFS= read -r -d '' file; do
+        if awk -v command="/$name" '$1 == "command:" && $2 == command { found=1 } END { exit found ? 0 : 1 }' "$file"; then
+          printf '%s\n' "$file"
+          break
+        fi
+      done
+  fi
 }
 
 allowed_agents_for_command() {
@@ -64,7 +78,7 @@ main() {
   echo "========================================================"
   echo ""
 
-  if [ ! -d "project/tickets" ]; then
+  if [ ! -d "docs/runtime/project/tickets" ]; then
     log_info "No tickets directory; skipping"
     exit 0
   fi
@@ -114,7 +128,7 @@ main() {
         errors=$((errors + 1))
       fi
     done
-  done < <(find project/tickets -name '*.json' -type f -print0)
+  done < <(find docs/runtime/project/tickets -name '*.json' -type f -print0)
 
   echo ""
   echo "========================================================"

package/{core/scripts → scripts}/validate-state.sh

@@ -35,10 +35,10 @@ NC='\033[0m'
 # ============================================================
 # Config
 # ============================================================
-TICKETS_DIR="project/tickets"
-BUGS_DIR="project/bugs"
-BACKLOG_FILE="project/backlog/backlog.json"
-SCHEMA_FILE="core/config/ticket.schema.json"
+TICKETS_DIR="docs/runtime/project/tickets"
+BUGS_DIR="docs/runtime/project/bugs"
+BACKLOG_FILE="docs/runtime/project/backlog/backlog.json"
+SCHEMA_FILE="docs/config/ticket.schema.json"
 
 # ============================================================
 # Allowed state transitions matrix (per RULE 06)
@@ -444,7 +444,7 @@ validate_backlog() {
 # Validate release governance records
 # ============================================================
 validate_releases() {
-  local releases_dir="project/releases"
+  local releases_dir="docs/runtime/project/releases"
 
   if [ ! -d "$releases_dir" ]; then
     return 0
@@ -606,6 +606,6 @@ else
   echo "════════════════════════════════════════════════════════"
   echo ""
   echo "Per RULE 06 (Approval Gates), all tickets must follow state machine."
-  echo "See: core/rules/06-approval-gates.md"
+  echo "See: rules/06-approval-gates.md"
   exit 1
 fi

package/{core/scripts → scripts}/workflow.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# core/scripts/workflow.sh
+# scripts/workflow.sh
 #
 # Executable handlers for AI Core state workflow commands.
 
@@ -38,7 +38,7 @@ agent_name() {
 }
 
 ticket_file() {
-  printf 'project/tickets/%s.json' "$1"
+  printf 'docs/runtime/project/tickets/%s.json' "$1"
 }
 
 slugify() {
@@ -50,7 +50,7 @@ slugify() {
 
 next_ticket_id() {
   local max_id
-  max_id=$(find project/tickets -name 'TICKET-*.json' -type f 2>/dev/null |
+  max_id=$(find docs/runtime/project/tickets -name 'TICKET-*.json' -type f 2>/dev/null |
     sed -E 's/.*TICKET-([0-9]+)\.json/\1/' |
     sort -n |
     tail -1)
@@ -79,7 +79,7 @@ hash_value() {
 }
 
 last_audit_hash() {
-  local audit_file="project/audit-log.jsonl"
+  local audit_file="docs/runtime/project/audit-log.jsonl"
   if [ ! -s "$audit_file" ]; then
     printf ''
     return 0
@@ -95,7 +95,7 @@ append_audit() {
   local reason="$5"
 
   mkdir -p project
-  local audit_file="project/audit-log.jsonl"
+  local audit_file="docs/runtime/project/audit-log.jsonl"
   local at by prev payload hash
   at=$(now_utc)
   by=$(agent_name)
@@ -159,8 +159,8 @@ transition_ticket() {
        }]' "$file" | write_json "$file"
 
   append_audit "$command" "$ticket_id" "$from_state" "$to_state" "$reason"
-  bash core/scripts/validate-state.sh "$ticket_id"
-  bash core/scripts/validate-permissions.sh
+  bash scripts/validate-state.sh "$ticket_id"
+  bash scripts/validate-permissions.sh
   log_pass "$ticket_id transitioned $from_state -> $to_state"
 }
 
@@ -181,7 +181,7 @@ cmd_analyze_requirements() {
     exit 1
   fi
 
-  mkdir -p project/tickets docs/project/specs
+  mkdir -p docs/runtime/project/tickets docs/project/specs
   local ticket_id file at by slug spec_path
   ticket_id=$(next_ticket_id)
   file=$(ticket_file "$ticket_id")
@@ -277,7 +277,7 @@ EOF
     }' > "$file"
 
   append_audit "/analyze-requirements" "$ticket_id" "null" "DRAFT" "Created from executable requirement intake"
-  bash core/scripts/validate-state.sh "$ticket_id"
+  bash scripts/validate-state.sh "$ticket_id"
   log_pass "Created $ticket_id"
   log_pass "Created $spec_path"
 }
@@ -349,7 +349,7 @@ Implement the ticket scope while preserving the approved acceptance criteria and
 
 ## Current Context
 
-- Read \`project/tickets/${ticket_id}.json\`.
+- Read \`docs/runtime/project/tickets/${ticket_id}.json\`.
 - Read the linked spec if present.
 - Inspect affected code before editing.
 
@@ -407,8 +407,8 @@ EOF
        }])' "$file" | write_json "$file"
 
   append_audit "/write-plan" "$ticket_id" "$status" "$status" "Implementation plan created"
-  bash core/scripts/validate-state.sh "$ticket_id"
-  bash core/scripts/validate-permissions.sh
+  bash scripts/validate-state.sh "$ticket_id"
+  bash scripts/validate-permissions.sh
   log_pass "Created $plan_path"
   log_pass "Linked plan from $file"
 }
@@ -452,7 +452,7 @@ cmd_smoke_test() {
     log_fail "$ticket_id status must be QA before QA evidence is written"
     exit 1
   fi
-  [ -n "$evidence_path" ] || evidence_path="project/test-runs/${ticket_id}-$(date -u +%Y%m%d%H%M%S).md"
+  [ -n "$evidence_path" ] || evidence_path="docs/runtime/project/test-runs/${ticket_id}-$(date -u +%Y%m%d%H%M%S).md"
   mkdir -p "$(dirname "$evidence_path")"
   if [ ! -f "$evidence_path" ]; then
     printf '# Smoke Test Evidence: %s\n\nGenerated by executable smoke-test gate at %s.\n' "$ticket_id" "$(now_utc)" > "$evidence_path"
@@ -478,8 +478,8 @@ cmd_smoke_test() {
 cmd_release() {
   local version="${1:-}"
   [ -n "$version" ] || { log_fail "Usage: /release vMAJOR.MINOR.PATCH"; exit 2; }
-  mkdir -p project/releases
-  local file="project/releases/${version}.json"
+  mkdir -p docs/runtime/project/releases
+  local file="docs/runtime/project/releases/${version}.json"
   if [ -f "$file" ]; then
     log_fail "Release record already exists: $file"
     exit 1
@@ -490,7 +490,7 @@ cmd_release() {
   jq --arg version "$version" --arg at "$at" --arg by "$by" \
     '.version = $version
      | .created_at = $at
-     | .created_by = $by' core/templates/release/release-record-template.json > "$file"
+     | .created_by = $by' templates/release/release-record-template.json > "$file"
   log_pass "Created release record $file"
 }
 

package/{core/skills → skills}/ai-core-commands/SKILL.md

@@ -5,7 +5,7 @@ description: Interpret AI Core slash-command text in Codex. Use when the user ty
 
 # AI Core Commands
 
-Codex plugins do not expose `core/commands/*.md` as native slash-command autocomplete. This skill makes AI Core command text executable through normal chat.
+Codex plugins do not expose `commands/*.md` as native slash-command autocomplete. This skill makes AI Core command text executable through normal chat.
 
 ## Mandatory Trigger
 
@@ -34,21 +34,21 @@ next TICKET-XXX
 
 1. Log the user request first:
    ```bash
-   AI_AGENT=codex bash core/scripts/log-user-request.sh "<user request text>"
+   AI_AGENT=codex bash scripts/log-user-request.sh "<user request text>"
    ```
 
 2. Resolve command metadata:
-   - Search `core/commands/**/<command-name>.md`.
+   - Search `commands/**/<command-name>.md`.
    - Read the command file.
    - Infer `owner_agent`, `requires_agents`, args, preconditions, postconditions, hard rules, and output format.
 
 3. Load the matching agent file when present:
-   - `core/agents/<owner_agent>.md`
+   - `agents/<owner_agent>.md`
 
 4. Execute the command in chat-first mode:
    - Use deterministic scripts only when the command file or workflow requires them.
    - Do not ask the user to run shell wrappers during normal use.
-   - Preserve all hard rules from `core/rules/00-global-rules.md`.
+   - Preserve all hard rules from `rules/00-global-rules.md`.
 
 5. Report:
    - Command executed
@@ -62,19 +62,19 @@ next TICKET-XXX
 Command files are stored under:
 
 ```text
-core/commands/
+commands/
 ```
 
 The command name maps to a Markdown file by removing the leading slash:
 
 ```text
-/analyze-requirements -> core/commands/**/analyze-requirements.md
-/request-log -> core/commands/**/request-log.md
+/analyze-requirements -> commands/**/analyze-requirements.md
+/request-log -> commands/**/request-log.md
 ```
 
 If multiple files match the same command name, stop and ask for clarification.
 
-If no file matches, say the command is not defined and suggest `/request-log`, `/setup-project`, or checking `core/commands/README.md`.
+If no file matches, say the command is not defined and suggest `/request-log`, `/setup-project`, or checking `commands/README.md`.
 
 ## Strict Rules
 

package/{core/skills → skills}/brainstorming/SKILL.md

@@ -14,7 +14,7 @@ Use this before implementation work, feature creation, behavior changes, or larg
 3. Propose 2-3 approaches with tradeoffs and a recommendation.
 4. Present a concise design for user approval.
 5. Save the approved spec to `docs/project/specs/TICKET-XXX-<slug>.md`.
-6. Link the spec from `project/tickets/TICKET-XXX.json` as `spec_path`.
+6. Link the spec from `docs/runtime/project/tickets/TICKET-XXX.json` as `spec_path`.
 7. Suggest `/groom-ticket TICKET-XXX`.
 
 ## Hard Gates

package/{core/skills → skills}/development-implement-task/SKILL.md

@@ -13,9 +13,9 @@ args:
   - name: ticket_id
     required: true
     format: "TICKET-XXX"
-    description: "Ticket ID from project/tickets/"
+    description: "Ticket ID from docs/runtime/project/tickets/"
 preconditions:
-  - ticket_exists: "project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/project/tickets/${ticket_id}.json"
   - ticket_status_in: [READY, IN_PROGRESS]
   - ticket_has_acceptance_criteria: true
   - no_uncommitted_changes_on_main: true
@@ -54,7 +54,7 @@ Before starting, the AI **MUST** check every condition below. If any condition f
 
 ### 1. Ticket exists
 ```bash
-test -f "project/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
+test -f "docs/runtime/project/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
 ```
 
 ### 2. Ticket status valid
@@ -90,8 +90,8 @@ Load `rules/07-definition-of-ready.md`. Verify the ticket passes every item. If
 │  → Read ticket JSON                             │
 │  → Read acceptance criteria                     │
 │  → Read related code (if ticket references it)  │
-│  → Read core/rules/02-code-quality.md       │
-│  → Read core/rules/05-testing-mandatory.md  │
+│  → Read rules/02-code-quality.md       │
+│  → Read rules/05-testing-mandatory.md  │
 ├─────────────────────────────────────────────────┤
 │  STEP 3: Create/checkout branch                 │
 │  → Branch name: feature/${TICKET_ID}-${slug}    │
@@ -99,7 +99,7 @@ Load `rules/07-definition-of-ready.md`. Verify the ticket passes every item. If
 │  → Example: feature/TICKET-123-reset-password   │
 ├─────────────────────────────────────────────────┤
 │  STEP 4: Update ticket status → IN_PROGRESS     │
-│  → Update project/tickets/${TICKET_ID}.json       │
+│  → Update docs/runtime/project/tickets/${TICKET_ID}.json       │
 │  → Add started_at timestamp                     │
 │  → Add assignee = "developer-agent"             │
 ├─────────────────────────────────────────────────┤
@@ -251,7 +251,7 @@ Ready for review. Key things to verify:
 
 ## 📊 Metrics Tracked
 
-After each run, log to `project/metrics/implement-task.jsonl`:
+After each run, log to `docs/runtime/project/metrics/implement-task.jsonl`:
 
 ```json
 {

package/{core/skills → skills}/meta-generate-views/SKILL.md

@@ -16,7 +16,7 @@ postconditions:
 
 # /generate-views
 
-> Generates human-readable views from `project/` without changing canonical state.
+> Generates human-readable views from `docs/runtime/project/` without changing canonical state.
 
 ## 🎯 Purpose
 
@@ -24,14 +24,14 @@ Help humans navigate many tickets without making duplicate sources of truth.
 
 ## 🔄 Execution Flow
 
-1. Load `project/backlog/backlog.json`.
+1. Load `docs/runtime/project/backlog/backlog.json`.
 2. Load tickets, bugs, sprints, and releases.
-3. Generate `project/views/backlog.md`.
-4. Generate `project/views/ready.md`.
-5. Generate `project/views/blocked.md`.
-6. Generate `project/views/by-epic.md`.
-7. Generate `project/views/by-sprint.md`.
-8. Generate `project/views/release-candidates.md`.
+3. Generate `docs/runtime/project/views/backlog.md`.
+4. Generate `docs/runtime/project/views/ready.md`.
+5. Generate `docs/runtime/project/views/blocked.md`.
+6. Generate `docs/runtime/project/views/by-epic.md`.
+7. Generate `docs/runtime/project/views/by-sprint.md`.
+8. Generate `docs/runtime/project/views/release-candidates.md`.
 9. Include generation timestamp and source files.
 
 ## 🔒 Hard Rules

package/{core/skills → skills}/meta-request-log/SKILL.md

@@ -15,14 +15,14 @@ args:
     default: 20
     description: "Number of recent user requests to show"
 preconditions:
-  - user_request_log_exists: "project/user-requests.jsonl"
+  - user_request_log_exists: "docs/runtime/project/user-requests.jsonl"
 postconditions:
   - request_log_reported: true
 ---
 
 # /request-log
 
-> Show recent user requests recorded in `project/user-requests.jsonl`.
+> Show recent user requests recorded in `docs/runtime/project/user-requests.jsonl`.
 
 ## 🎯 Purpose
 
@@ -37,7 +37,7 @@ Give the user an auditable view of what they asked the AI to do.
 
 ## 🔄 Execution Flow
 
-1. Read `project/user-requests.jsonl`.
+1. Read `docs/runtime/project/user-requests.jsonl`.
 2. Show the most recent N entries, default 20.
 3. Include timestamp, agent, detected command, ticket ID, and sanitized request text.
 4. If the log is missing, tell the user to run `/setup-project`.
@@ -48,7 +48,7 @@ Give the user an auditable view of what they asked the AI to do.
 The command **MUST NOT** attempt to reconstruct secrets from `request_hash` or any redacted value.
 
 ### RULE RL-002: Log is append-only
-Existing `project/user-requests.jsonl` entries **MUST NOT** be edited. Corrections require a new request entry.
+Existing `docs/runtime/project/user-requests.jsonl` entries **MUST NOT** be edited. Corrections require a new request entry.
 
 ## 📤 Output Format
 

package/{core/skills → skills}/meta-sprint-report/SKILL.md

@@ -19,7 +19,7 @@ postconditions:
 
 # /sprint-report
 
-> Produces a factual sprint health and outcome report from `project/`.
+> Produces a factual sprint health and outcome report from `docs/runtime/project/`.
 
 ## 🎯 Purpose
 
@@ -33,7 +33,7 @@ Give the team an auditable view of commitment, progress, blockers, carryover, de
 4. List work by state.
 5. Identify aging tickets and unresolved blockers.
 6. Summarize risks, decisions, and recommended next actions.
-7. Save report under `project/sprints/` or `project/metrics/` if requested.
+7. Save report under `docs/runtime/project/sprints/` or `docs/runtime/project/metrics/` if requested.
 
 ## 🔒 Hard Rules
 

package/{core/skills → skills}/meta-sync-platforms/SKILL.md

@@ -19,23 +19,23 @@ postconditions:
 
 # /sync-platforms
 
-> Exports `core/` source-of-truth specs to Claude Code, Cursor, and Windsurf config files.
+> Exports root-level framework source-of-truth specs to Claude Code, Cursor, and Windsurf config files.
 
 ## 🎯 Purpose
 
-Keep all supported AI tools aligned with the same agents, commands, and rules while editing only `core/` as the canonical source.
+Keep all supported AI tools aligned with the same agents, commands, and rules while editing only root-level framework folders as the canonical source.
 
 ## 🔄 Execution Flow
 
-1. Verify `core/scripts/sync-platforms.sh` exists.
-2. Run `bash core/scripts/sync-platforms.sh`.
+1. Verify `scripts/sync-platforms.sh` exists.
+2. Run `bash scripts/sync-platforms.sh`.
 3. Review generated `.claude/`, `.cursor/rules/`, `.windsurfrules`, and `CLAUDE.md`.
 4. Confirm generated files should be committed.
 5. Report created/updated files.
 
 ## 🔒 Hard Rules
 
-- Source changes MUST be made in `core/`, not generated exports.
+- Source changes MUST be made in root-level framework folders, not generated exports.
 - MUST review generated files before commit.
 - MUST rerun after changing agents, commands, or rules.
 - MUST NOT delete user custom platform config without confirmation.

package/{core/skills → skills}/meta-ticket-health/SKILL.md

@@ -20,7 +20,7 @@ postconditions:
 
 # /ticket-health
 
-> Finds stale, blocked, inconsistent, or under-specified tickets in `project/tickets/`.
+> Finds stale, blocked, inconsistent, or under-specified tickets in `docs/runtime/project/tickets/`.
 
 ## 🎯 Purpose
 

package/{core/skills → skills}/meta-validate-audit-log/SKILL.md

@@ -23,7 +23,7 @@ postconditions:
 
 ## Purpose
 
-Detect manual edits to `project/audit-log.jsonl`. Executable workflow handlers append records with `prev_hash` and `hash`; this command recomputes the chain.
+Detect manual edits to `docs/runtime/project/audit-log.jsonl`. Executable workflow handlers append records with `prev_hash` and `hash`; this command recomputes the chain.
 
 ## Chat Usage
 
@@ -31,7 +31,7 @@ Detect manual edits to `project/audit-log.jsonl`. Executable workflow handlers a
 /validate-audit-log
 ```
 
-The AI may call `core/scripts/validate-audit-log.sh` internally and must summarize the result.
+The AI may call `scripts/validate-audit-log.sh` internally and must summarize the result.
 
 ## Hard Rules
 

package/{core/skills → skills}/meta-validate-docs/SKILL.md

@@ -29,7 +29,7 @@ postconditions:
 
 ## Purpose
 
-Catch missing docs before review or release. In chat, use `/validate-docs`; the AI may call `core/scripts/validate-docs.sh` internally and must summarize the result.
+Catch missing docs before review or release. In chat, use `/validate-docs`; the AI may call `scripts/validate-docs.sh` internally and must summarize the result.
 
 ## Execution Flow
 

package/{core/skills → skills}/meta-validate-permissions/SKILL.md

@@ -24,7 +24,7 @@ postconditions:
 
 ## Purpose
 
-Make role boundaries mechanically enforceable by comparing `project/tickets/*.json` history entries with `core/commands/**` command ownership metadata.
+Make role boundaries mechanically enforceable by comparing `docs/runtime/project/tickets/*.json` history entries with `commands/**` command ownership metadata.
 
 ## Chat Usage
 
@@ -38,7 +38,7 @@ Make role boundaries mechanically enforceable by comparing `project/tickets/*.js
 `state_history[].by_agent` must match the command `owner_agent` or `requires_agents`.
 
 ### RULE VP-002: Unknown commands fail
-Any `by_command` value without a matching `core/commands/**/<name>.md` file blocks validation.
+Any `by_command` value without a matching `commands/**/<name>.md` file blocks validation.
 
 ### RULE VP-003: No self-approval
 If `assignee` is recorded, the same agent cannot approve review-to-QA or DONE transitions.

package/{core/skills → skills}/meta-validate-state/SKILL.md

@@ -19,7 +19,7 @@ postconditions:
 
 # /validate-state
 
-> Validates `project/` integrity, backlog references, ticket schema, and allowed state transitions.
+> Validates `docs/runtime/project/` integrity, backlog references, ticket schema, and allowed state transitions.
 
 ## 🎯 Purpose
 
@@ -28,9 +28,9 @@ Catch corrupted backlog data, missing ticket references, skipped transitions, mi
 ## 🔄 Execution Flow
 
 1. Verify `jq` is installed.
-2. In chat, run `/validate-state` with optional ticket ID. The AI may call `core/scripts/validate-state.sh` internally.
-3. Validate `project/backlog/backlog.json` references existing tickets when validating all state.
-4. If available, run JSON schema validation against `core/config/ticket.schema.json` and `core/config/backlog.schema.json`.
+2. In chat, run `/validate-state` with optional ticket ID. The AI may call `scripts/validate-state.sh` internally.
+3. Validate `docs/runtime/project/backlog/backlog.json` references existing tickets when validating all state.
+4. If available, run JSON schema validation against `docs/config/ticket.schema.json` and `docs/config/backlog.schema.json`.
 5. Report failures with file path, field, and recovery command.
 6. Block workflow if validation fails.
 

package/{core/skills → skills}/planning-analyze-requirements/SKILL.md

@@ -62,13 +62,13 @@ Turn free-text requirement (email, Slack, voice note) into a structured ticket w
 
 Check before starting. **ABORT** if any check fails.
 
-### 1. `core/` initialized
+### 1. Root-level framework folders initialized
 ```bash
-test -d "project/tickets" || ABORT "Run /setup-project first"
+test -d "docs/runtime/project/tickets" || ABORT "Run /setup-project first"
 ```
 
 ### 2. BA agent available
-Check `core/agents/business-analyst.md` exists and is enabled in config.
+Check `agents/business-analyst.md` exists and is enabled in config.
 
 ### 3. Requirement text is not empty
 If empty or < 10 chars → ABORT and ask for the actual requirement.
@@ -139,13 +139,13 @@ If empty or < 10 chars → ABORT and ask for the actual requirement.
 │   - External dependencies (3rd party API)?               │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 8: Generate ticket ID                               │
-│   - Read project/tickets/                         │
+│   - Read docs/runtime/project/tickets/                         │
 │   - Find highest TICKET-NNN                              │
 │   - Increment: TICKET-NNN+1                              │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 9: Write ticket JSON                                │
-│   Path: project/tickets/TICKET-XXX.json           │
-│   Schema: core/config/ticket.schema.json             │
+│   Path: docs/runtime/project/tickets/TICKET-XXX.json           │
+│   Schema: docs/config/ticket.schema.json             │
 │   State: DRAFT                                           │
 │   created_by: "business-analyst-agent"                   │
 ├──────────────────────────────────────────────────────────┤
@@ -194,7 +194,7 @@ SEV-1 bug **MUST** trigger hotfix notification:
 
 ### RULE AR-009: No duplicate tickets
 Before creating, **MUST** search existing tickets for similar work:
-- Grep titles in `project/tickets/*.json`
+- Grep titles in `docs/runtime/project/tickets/*.json`
 - If high similarity (>80%) → flag to user, ask if duplicate
 
 ### RULE AR-010: Complete source tracking
@@ -297,7 +297,7 @@ Estimated: 40% support load reduction if self-service reset works.
 - [ ] Email template: existing template system or custom?
 
 ### Ticket File
-Created: `project/tickets/TICKET-042.json`
+Created: `docs/runtime/project/tickets/TICKET-042.json`
 
 ---
 HANDOFF → tech-lead
@@ -404,7 +404,7 @@ Then Login fails, no SQL injection possible
 3. **Dev**: Pair with Tech Lead on fix
 
 ### Ticket File
-Created: `project/tickets/TICKET-101.json`
+Created: `docs/runtime/project/tickets/TICKET-101.json`
 
 ---
 HANDOFF → scrum-master + tech-lead (URGENT)
@@ -433,7 +433,7 @@ Action needed: /hotfix TICKET-101
 
 ## 📊 Metrics Tracked
 
-Log to `project/metrics/analyze-requirements.jsonl`:
+Log to `docs/runtime/project/metrics/analyze-requirements.jsonl`:
 
 ```json
 {

package/{core/skills → skills}/planning-backlog-status/SKILL.md

@@ -11,14 +11,14 @@ consults_agents:
 model_preference: sonnet
 args: []
 preconditions:
-  - backlog_exists: "project/backlog/backlog.json"
+  - backlog_exists: "docs/runtime/project/backlog/backlog.json"
 postconditions:
   - backlog_report_generated: true
 ---
 
 # /backlog-status
 
-> Reports backlog health from `project/backlog/backlog.json` and linked ticket files.
+> Reports backlog health from `docs/runtime/project/backlog/backlog.json` and linked ticket files.
 
 ## 🎯 Purpose
 
@@ -26,8 +26,8 @@ Show whether the backlog is prioritized, actionable, and aligned with ticket sta
 
 ## 🔄 Execution Flow
 
-1. Load `project/backlog/backlog.json`.
-2. Load referenced `project/tickets/TICKET-XXX.json` files.
+1. Load `docs/runtime/project/backlog/backlog.json`.
+2. Load referenced `docs/runtime/project/tickets/TICKET-XXX.json` files.
 3. Detect missing ticket references.
 4. Detect duplicate ranks or duplicate ticket IDs.
 5. Group by priority, epic, and status.
@@ -36,8 +36,8 @@ Show whether the backlog is prioritized, actionable, and aligned with ticket sta
 
 ## 🔒 Hard Rules
 
-- Backlog ordering source of truth is `project/backlog/backlog.json`.
-- Ticket detail source of truth is `project/tickets/TICKET-XXX.json`.
+- Backlog ordering source of truth is `docs/runtime/project/backlog/backlog.json`.
+- Ticket detail source of truth is `docs/runtime/project/tickets/TICKET-XXX.json`.
 - MUST NOT duplicate full ticket content in backlog reports.
 - MUST flag backlog items pointing to missing tickets.
 

package/{core/skills → skills}/planning-groom-ticket/SKILL.md

@@ -17,7 +17,7 @@ args:
     format: "TICKET-XXX"
     description: "Ticket ID to groom"
 preconditions:
-  - ticket_exists: "project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/project/tickets/${ticket_id}.json"
   - ticket_status: DRAFT
   - has_user_story: true
   - has_acceptance_criteria: true (min 3 scenarios)
@@ -60,7 +60,7 @@ After BA creates a DRAFT ticket, Tech Lead must:
 
 ### 1. Ticket exists
 ```bash
-test -f "project/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
+test -f "docs/runtime/project/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
 ```
 
 ### 2. Ticket status = DRAFT
@@ -300,7 +300,7 @@ Block transition to GROOMED until ADR created OR explicit decision to defer.
 ### Ticket Update
 
 **State**: DRAFT → GROOMED ✅ (assuming questions minor)
-**Updated**: `project/tickets/TICKET-042.json`
+**Updated**: `docs/runtime/project/tickets/TICKET-042.json`
 
 Added fields:
 - `estimate`: `{ story_points: 5, estimated_by: "tech-lead-agent", estimated_at: "..." }`
@@ -420,7 +420,7 @@ State: DRAFT → BLOCKED (pending split)
 
 ## 📊 Metrics Tracked
 
-Log to `project/metrics/groom-ticket.jsonl`:
+Log to `docs/runtime/project/metrics/groom-ticket.jsonl`:
 
 ```json
 {