ai-core-framework 0.2.0 → 0.4.0

package/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="config/ticket.schema.json"
+TICKETS_DIR="docs/runtime/tickets"
+BUGS_DIR="docs/runtime/bugs"
+BACKLOG_FILE="docs/runtime/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/releases"
 
   if [ ! -d "$releases_dir" ]; then
     return 0

package/scripts/workflow.sh

@@ -38,7 +38,7 @@ agent_name() {
 }
 
 ticket_file() {
-  printf 'project/tickets/%s.json' "$1"
+  printf 'docs/runtime/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/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/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/audit-log.jsonl"
   local at by prev payload hash
   at=$(now_utc)
   by=$(agent_name)
@@ -181,7 +181,7 @@ cmd_analyze_requirements() {
     exit 1
   fi
 
-  mkdir -p project/tickets docs/project/specs
+  mkdir -p docs/runtime/tickets docs/project/specs
   local ticket_id file at by slug spec_path
   ticket_id=$(next_ticket_id)
   file=$(ticket_file "$ticket_id")
@@ -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/tickets/${ticket_id}.json\`.
 - Read the linked spec if present.
 - Inspect affected code before editing.
 
@@ -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/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/releases
+  local file="docs/runtime/releases/${version}.json"
   if [ -f "$file" ]; then
     log_fail "Release record already exists: $file"
     exit 1

package/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/tickets/TICKET-XXX.json` as `spec_path`.
 7. Suggest `/groom-ticket TICKET-XXX`.
 
 ## Hard Gates

package/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/tickets/"
 preconditions:
-  - ticket_exists: "project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/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/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
 ```
 
 ### 2. Ticket status valid
@@ -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/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/metrics/implement-task.jsonl`:
 
 ```json
 {

package/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/` 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/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/views/backlog.md`.
+4. Generate `docs/runtime/views/ready.md`.
+5. Generate `docs/runtime/views/blocked.md`.
+6. Generate `docs/runtime/views/by-epic.md`.
+7. Generate `docs/runtime/views/by-sprint.md`.
+8. Generate `docs/runtime/views/release-candidates.md`.
 9. Include generation timestamp and source files.
 
 ## 🔒 Hard Rules

package/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/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/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/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/user-requests.jsonl` entries **MUST NOT** be edited. Corrections require a new request entry.
 
 ## 📤 Output Format
 

package/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/`.
 
 ## 🎯 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/sprints/` or `docs/runtime/metrics/` if requested.
 
 ## 🔒 Hard Rules
 

package/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/tickets/`.
 
 ## 🎯 Purpose
 

package/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/audit-log.jsonl`. Executable workflow handlers append records with `prev_hash` and `hash`; this command recomputes the chain.
 
 ## Chat Usage
 

package/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 `commands/**` command ownership metadata.
+Make role boundaries mechanically enforceable by comparing `docs/runtime/tickets/*.json` history entries with `commands/**` command ownership metadata.
 
 ## Chat Usage
 

package/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/` integrity, backlog references, ticket schema, and allowed state transitions.
 
 ## 🎯 Purpose
 
@@ -29,8 +29,8 @@ Catch corrupted backlog data, missing ticket references, skipped transitions, mi
 
 1. Verify `jq` is installed.
 2. In chat, run `/validate-state` with optional ticket ID. The AI may call `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 `config/ticket.schema.json` and `config/backlog.schema.json`.
+3. Validate `docs/runtime/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/skills/planning-analyze-requirements/SKILL.md

@@ -64,7 +64,7 @@ Check before starting. **ABORT** if any check fails.
 
 ### 1. Root-level framework folders initialized
 ```bash
-test -d "project/tickets" || ABORT "Run /setup-project first"
+test -d "docs/runtime/tickets" || ABORT "Run /setup-project first"
 ```
 
 ### 2. BA agent available
@@ -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/tickets/                         │
 │   - Find highest TICKET-NNN                              │
 │   - Increment: TICKET-NNN+1                              │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 9: Write ticket JSON                                │
-│   Path: project/tickets/TICKET-XXX.json           │
-│   Schema: config/ticket.schema.json             │
+│   Path: docs/runtime/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/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/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/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/metrics/analyze-requirements.jsonl`:
 
 ```json
 {

package/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/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/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/backlog/backlog.json`.
+2. Load referenced `docs/runtime/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/backlog/backlog.json`.
+- Ticket detail source of truth is `docs/runtime/tickets/TICKET-XXX.json`.
 - MUST NOT duplicate full ticket content in backlog reports.
 - MUST flag backlog items pointing to missing tickets.
 

package/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/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/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/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/metrics/groom-ticket.jsonl`:
 
 ```json
 {

package/skills/planning-mark-ready/SKILL.md

@@ -18,7 +18,7 @@ args:
     format: "TICKET-XXX"
     description: "GROOMED ticket to verify against Definition of Ready"
 preconditions:
-  - ticket_exists: "project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/tickets/${ticket_id}.json"
   - ticket_status: GROOMED
   - has_estimate: true
   - has_acceptance_criteria: true
@@ -46,7 +46,7 @@ Manual only:
 
 ## 📋 Preconditions, STRICT
 
-1. Ticket exists in `project/tickets/`.
+1. Ticket exists in `docs/runtime/tickets/`.
 2. Ticket status is exactly `GROOMED`.
 3. Ticket has user story, acceptance criteria, estimate, technical approach, risks, and dependencies.
 4. Ticket estimate is one of `1, 2, 3, 5, 8`.

package/skills/planning-plan-refactor/SKILL.md

@@ -32,13 +32,13 @@ Plan large refactors without putting project-specific design into framework sour
 
 ## 🔄 Execution Flow
 
-1. Load `config/project-structure.yaml`.
+1. Load `docs/config/project-structure.yaml`.
 2. Inspect affected code areas and docs.
 3. Identify current problem, target state, constraints, and risks.
 4. Determine whether ADR is required.
 5. Create `docs/runtime/refactor/<slug>-refactor-plan.md` from `templates/technical/refactor-plan-template.md`.
-6. Propose ticket breakdown for `project/tickets/`.
-7. Propose backlog entries for `project/backlog/backlog.json`.
+6. Propose ticket breakdown for `docs/runtime/tickets/`.
+7. Propose backlog entries for `docs/runtime/backlog/backlog.json`.
 8. Define testing, rollout, and rollback plan.
 9. HANDOFF to BA for ticket creation or Tech Lead for ADR.
 

package/skills/planning-plan-sprint/SKILL.md

@@ -35,7 +35,7 @@ postconditions:
 
 ## 🎯 Purpose
 
-Build a realistic sprint commitment. It selects only `READY` tickets, respects configured sprint capacity, checks dependencies, and writes the sprint plan to `project/sprints/`.
+Build a realistic sprint commitment. It selects only `READY` tickets, respects configured sprint capacity, checks dependencies, and writes the sprint plan to `docs/runtime/sprints/`.
 
 ## 🚦 Trigger
 
@@ -46,7 +46,7 @@ Manual at sprint planning:
 
 ## 📋 Preconditions, STRICT
 
-1. `config/project-config.yaml` exists.
+1. `docs/config/project-config.yaml` exists.
 2. `/validate-state` passes.
 3. At least one ticket has status `READY`.
 4. Sprint capacity is configured under `scrum.sprint_capacity_points`.
@@ -63,9 +63,9 @@ Manual at sprint planning:
 6. Select tickets until capacity is reached.
 7. Reserve capacity for bugs, review, QA, and operational work.
 8. Validate no selected ticket violates DoR.
-9. Write `project/sprints/SPRINT-XXX.json` with goal, dates, capacity, committed tickets, risks, and assumptions.
+9. Write `docs/runtime/sprints/SPRINT-XXX.json` with goal, dates, capacity, committed tickets, risks, and assumptions.
 10. Update selected tickets with `sprint_id`.
-11. Append planning metrics to `project/metrics/sprint-planning.jsonl`.
+11. Append planning metrics to `docs/runtime/metrics/sprint-planning.jsonl`.
 12. Output sprint goal, commitment, risks, and handoffs.
 
 ## 🔒 Hard Rules

package/skills/planning-prioritize-backlog/SKILL.md

@@ -16,14 +16,14 @@ args:
     enum: [moscow, rice, manual]
     default: moscow
 preconditions:
-  - backlog_exists: "project/backlog/backlog.json"
+  - backlog_exists: "docs/runtime/backlog/backlog.json"
 postconditions:
   - backlog_order_updated: true
 ---
 
 # /prioritize-backlog
 
-> Updates backlog ranking in `project/backlog/backlog.json` using MoSCoW, RICE, dependencies, and stakeholder input.
+> Updates backlog ranking in `docs/runtime/backlog/backlog.json` using MoSCoW, RICE, dependencies, and stakeholder input.
 
 ## 🎯 Purpose
 

package/skills/planning-write-plan/SKILL.md

@@ -42,7 +42,7 @@ Turn a groomed or ready ticket into a concrete execution plan before coding star
 
 ## Execution Flow
 
-1. Read `project/tickets/TICKET-XXX.json`.
+1. Read `docs/runtime/tickets/TICKET-XXX.json`.
 2. Read `spec_path` if present.
 3. Inspect relevant code/docs just enough to identify affected files and test strategy.
 4. Create `docs/project/plans/TICKET-XXX-<slug>-plan.md`.

package/skills/project-detect-stack/SKILL.md

@@ -21,7 +21,7 @@ postconditions:
 
 ## 🎯 Purpose
 
-Populate or validate `config/project-config.yaml` from actual repository evidence instead of guesses.
+Populate or validate `docs/config/project-config.yaml` from actual repository evidence instead of guesses.
 
 ## 🚦 Trigger
 

package/skills/project-discover-codebase/SKILL.md

@@ -37,13 +37,13 @@ Give AI agents shared context before implementation and review. The output helps
 
 ## 🔄 Execution Flow
 
-1. Load `config/project-config.yaml`.
+1. Load `docs/config/project-config.yaml`.
 2. Enumerate top-level directories and identify application, test, config, docs, scripts, and infra areas.
 3. Identify entry points, routes/controllers, domain modules, data access, jobs/workers, and shared libraries.
 4. Identify test layout and command coverage.
 5. Identify architecture docs and ADRs.
 6. Identify external integrations and environment assumptions.
-7. Produce `project/codebase-map.md` or update existing map with timestamp.
+7. Produce `docs/runtime/codebase-map.md` or update existing map with timestamp.
 8. List risks, missing docs, and recommended follow-up tickets.
 
 ## 🔒 Hard Rules

package/skills/project-setup-project/SKILL.md

@@ -44,18 +44,18 @@ Manual after copying root-level framework folders into a project:
 2. `README.md` exists.
 3. `templates/project/project-config.yaml` exists.
 4. `templates/project/project-structure.yaml` exists.
-5. User has permission to create `config/`, `project/`, `docs/project/`, `docs/runtime/`, `.claude/`, `.cursor/`, `.windsurfrules`, and `CLAUDE.md`.
+5. User has permission to create `docs/config/`, `docs/runtime/`, `docs/project/`, `.claude/`, `.cursor/`, `.windsurfrules`, and `CLAUDE.md`.
 
 ## 🔄 Execution Flow
 
 1. Confirm repo root and framework folder locations.
-2. Create `config/` if missing.
-3. Copy `templates/project/project-config.yaml` to `config/project-config.yaml` if missing.
-4. Copy `templates/project/project-structure.yaml` to `config/project-structure.yaml` if missing.
+2. Create `docs/config/` if missing.
+3. Copy `templates/project/project-config.yaml` to `docs/config/project-config.yaml` if missing.
+4. Copy `templates/project/project-structure.yaml` to `docs/config/project-structure.yaml` if missing.
 5. Ask for missing project fields or infer with `/detect-stack`.
-6. Create required `project/` directories: tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, prs.
+6. Create required `docs/runtime/` directories: tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, prs.
 7. Create required docs namespaces: `docs/project/` for project/product requirements and `docs/runtime/` for operational AI Core documentation.
-8. Create `project/backlog/backlog.json` and `project/user-requests.jsonl` if missing.
+8. Create `docs/runtime/backlog/backlog.json` and `docs/runtime/user-requests.jsonl` if missing.
 9. Run `bash scripts/setup-project.sh` when shell access is available, or perform steps 2-8 manually.
 10. Confirm `scripts/` contains the portable enforcement scripts.
 11. Install portable `.github/workflows/ai-core-governance.yml` if missing.
@@ -73,16 +73,16 @@ If config values already exist, preserve them unless user confirms change.
 Generated `.claude/`, `.cursor/`, and `.windsurfrules` files are exports. Source changes belong in root-level framework folders.
 
 ### RULE SP-003: No product code changes
-Setup modifies AI runtime/config files only: `config/`, `project/`, `docs/project/`, `docs/runtime/`, generated platform config, and optional docs scaffolding. It MUST NOT modify production source code.
+Setup modifies AI runtime/config files only: `docs/config/`, `docs/runtime/`, `docs/project/`, generated platform config, and optional docs scaffolding. It MUST NOT modify production source code.
 
 ### RULE SP-004: State directories required
-A project is not ready until `project/` contains directories for tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, and prs.
+A project is not ready until `docs/runtime/` contains directories for tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, and prs.
 
 ### RULE SP-004a: User request log required
-A project is not ready until `project/user-requests.jsonl` exists. Every AI-handled user request **MUST** be logged there before substantive work begins.
+A project is not ready until `docs/runtime/user-requests.jsonl` exists. Every AI-handled user request **MUST** be logged there before substantive work begins.
 
 ### RULE SP-005: Framework folders remain framework-only
-Project-specific state and config MUST NOT be written under framework source folders. Use `project/` and `config/`.
+Project-specific state and config MUST NOT be written under framework source folders. Use `docs/runtime/` and `docs/config/`.
 
 ### RULE SP-006: `scripts/` is canonical
 Portable enforcement scripts live under `scripts/`.

package/skills/qa-bug-status/SKILL.md

@@ -24,7 +24,7 @@ Give QA, Scrum Master, and Tech Lead a clear picture of defect health.
 
 ## 🔄 Execution Flow
 
-1. Load `project/bugs/*.json`.
+1. Load `docs/runtime/bugs/*.json`.
 2. Group bugs by severity and status.
 3. Identify stale bugs and missing owners.
 4. Identify release-blocking bugs.