arcane-cli 0.15.6 → 0.15.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (25) hide show
  1. package/dist/assets/.arcane/governance/portable-bootstrap.md +20 -13
  2. package/dist/assets/.github/prompts/spell-architect.prompt.md +3 -3
  3. package/dist/assets/.github/prompts/spell-bootstrap-business.prompt.md +1 -1
  4. package/dist/assets/.github/prompts/spell-brainstorm.prompt.md +2 -2
  5. package/dist/assets/.github/prompts/spell-bug.prompt.md +6 -6
  6. package/dist/assets/.github/prompts/spell-check-drift.prompt.md +1 -1
  7. package/dist/assets/.github/prompts/spell-close-session.prompt.md +1 -1
  8. package/dist/assets/.github/prompts/spell-commit-work.prompt.md +15 -14
  9. package/dist/assets/.github/prompts/spell-enchant.prompt.md +8 -8
  10. package/dist/assets/.github/prompts/spell-full-cycle.prompt.md +6 -6
  11. package/dist/assets/.github/prompts/spell-implement.prompt.md +3 -3
  12. package/dist/assets/.github/prompts/spell-open-session.prompt.md +11 -11
  13. package/dist/assets/.github/prompts/spell-plan.prompt.md +2 -2
  14. package/dist/assets/.github/prompts/spell-present-arcane.prompt.md +5 -5
  15. package/dist/assets/.github/prompts/spell-product-review.prompt.md +1 -1
  16. package/dist/assets/.github/prompts/spell-review.prompt.md +3 -3
  17. package/dist/assets/.github/prompts/spell-scope.prompt.md +7 -7
  18. package/dist/assets/.github/prompts/spell-ship.prompt.md +5 -5
  19. package/dist/assets/.github/prompts/spell-suggest-feature.prompt.md +4 -4
  20. package/dist/assets/.github/prompts/spell-test.prompt.md +3 -3
  21. package/dist/assets/README.md +14 -0
  22. package/dist/assets/project.md +26 -0
  23. package/dist/index.js +3 -1
  24. package/dist/index.js.map +1 -1
  25. package/package.json +2 -2
package/dist/assets/.arcane/governance/portable-bootstrap.md CHANGED
@@ -38,14 +38,21 @@ Paste this entire file into any AI client (Claude web, ChatGPT, etc.) to give it
38
38
 
39
39
  ## Key Files
40
40
 
41
- | Need | File |
42
- | ------------------ | ------------------------------------- |
43
- | Full rules | `governance/universal-agent-rules.md` |
44
- | Project overview | `project.md` |
45
- | Decisions log | `DECISIONS.md` |
46
- | Agent policies | `agents/agent-policies.md` |
47
- | Git conventions | `governance/git-conventions.md` |
48
- | AI context summary | `ai-context/system-prompt-context.md` |
41
+ | Need | File |
42
+ | ------------------ | --------------------------------------------- |
43
+ | Full rules | `.arcane/governance/universal-agent-rules.md` |
44
+ | Project overview | `project.md` |
45
+ | Decisions log | `DECISIONS.md` |
46
+ | Agent policies | `.arcane/governance/agent-policies.md` |
47
+ | Git conventions | `.arcane/governance/git-conventions.md` |
48
+ | AI context summary | `ai-context/system-prompt-context.md` |
49
+
50
+ ## Where Documents Live
51
+
52
+ - **Framework-managed standards:** `.arcane/governance/`. Spells reference this single installed layer; do not create a duplicate root `governance/` tree.
53
+ - **Project-owned orientation and continuity:** `README.md`, `project.md`, `TODO.md`, `DECISIONS.md`, `ai-context/`, and `journal/`. Arcane creates missing files once and preserves existing content.
54
+ - **Project/domain documents:** use explicit descriptive paths such as `docs/`, `security/`, `infrastructure/`, or a configured business root. These add project context alongside framework standards.
55
+ - **Overrides are not yet supported:** editing a managed `.arcane/governance/` standard can be replaced by `arcane update`. Additive project documents are safe; overriding a shipped standard requires the open customization/override model.
49
56
 
50
57
  ## Documentation Format
51
58
 
@@ -53,11 +60,11 @@ Every doc uses YAML frontmatter: `title`, `audience` (human/ai/both), `last_upda
53
60
 
54
61
  ## Naming Tiers
55
62
 
56
- | Tier | Style | Examples |
57
- | --------- | --------------- | ----------------------------------------- |
58
- | Machines | Iconic names | Atlas, Voyager |
63
+ | Tier | Style | Examples |
64
+ | --------- | --------------- | ---------------------------------------- |
65
+ | Machines | Iconic names | Atlas, Voyager |
59
66
  | AI Agents | Persona + role | Merlin — CTO, {AGENT_NAME} — Product Ops |
60
- | Systems | Functional slug | `inventory-api`, `orders-worker` |
67
+ | Systems | Functional slug | `inventory-api`, `orders-worker` |
61
68
 
62
69
  ## Version Control Host
63
70
 
@@ -98,4 +105,4 @@ Development follows the **Spell Loop** — structured planning phases feeding an
98
105
  - `spell-explain-concept` — Break down complex architecture concepts
99
106
  - `spell-generate-bot-icons` — Create agent personas and icons
100
107
 
101
- Full reference: See `governance/development-methodology.md` in the repo.
108
+ Full reference: See `.arcane/governance/development-methodology.md` in the repo.
package/dist/assets/.github/prompts/spell-architect.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This prompt takes a PRD and produces architecture decisions plus an implementable story breakdown.
11
11
  - It follows a structured solutioning pattern — progressive context chain from requirements to implementation plan.
12
12
  - Outputs `architecture.md` and `stories.json` that feed into `spell-implement`.
13
- - See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
13
+ - See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
14
14
 
15
15
  ---
16
16
 
@@ -18,8 +18,8 @@ Generate architecture decisions and story breakdown from the provided PRD.
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology and stories.json format
22
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage requirements
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology and stories.json format
22
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage requirements
23
23
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect and extend
24
24
 
25
25
  Workflow:
package/dist/assets/.github/prompts/spell-bootstrap-business.prompt.md CHANGED
@@ -24,7 +24,7 @@ If any required value is missing, ask only for missing fields.
24
24
  Use these files first (each is optional — if missing, proceed as noted):
25
25
 
26
26
  - [playbooks/new-business-setup.md](../../playbooks/new-business-setup.md) — setup playbook. If `playbooks/` doesn't exist, skip and derive steps from the business-type checklist below.
27
- - [naming-conventions.md](../../naming-conventions.md) — slug/file naming rules. If missing, default to lowercase-with-dashes slugs.
27
+ - [naming-conventions.md](../../.arcane/governance/naming-conventions.md) — slug/file naming rules. If missing, default to lowercase-with-dashes slugs.
28
28
  - [ventures/\_template/overview.md](../../ventures/_template/overview.md) — overview template. If missing, generate a minimal overview from the fields below.
29
29
  - [README.md](../../README.md) — repo navigation. If missing, skip cross-linking.
30
30
  - [project.md](../../project.md) — project context. If missing, skip.
package/dist/assets/.github/prompts/spell-brainstorm.prompt.md CHANGED
@@ -18,10 +18,10 @@ Explore the given problem space and generate solution options.
18
18
 
19
19
  Use these files for context. Each is **optional** — if a file is missing, proceed without it and note the gap in your output so the user knows what wasn't consulted:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology. _If missing:_ proceed with general SDLC reasoning.
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology. _If missing:_ proceed with general SDLC reasoning.
22
22
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs (to avoid contradicting decided patterns). _If missing:_ assume no decided patterns and state that ADR conflicts could not be checked.
23
23
  - [project.md](../../project.md) — Project goals and business context. _If missing:_ infer context from the problem statement and ask a clarifying question if goals are unclear.
24
- - [naming-conventions.md](../../naming-conventions.md) — Agent roster and roles. _If missing:_ proceed without role references.
24
+ - [naming-conventions.md](../../.arcane/governance/naming-conventions.md) — Agent roster and roles. _If missing:_ proceed without role references.
25
25
  - [TODO.md](../../../TODO.md) — In-progress work (referenced in step 4). _If missing:_ skip the in-progress-work cross-check and note it.
26
26
 
27
27
  ---
package/dist/assets/.github/prompts/spell-bug.prompt.md CHANGED
@@ -11,7 +11,7 @@ agent: agent
11
11
  - It records the bug in your configured tracker (external provider) or `TODO.md` (internal mode) and links the fix commit to it.
12
12
  - Output is a working fix with tests, committed using Conventional Commits format.
13
13
  - **When to use:** you have a concrete defect — wrong/broken behavior versus expected. If the report is actually a request for *new* behavior, route to `spell-suggest-feature` instead. For small non-blocking cleanups discovered along the way, capture them with `spell-todo`.
14
- - See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
14
+ - See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
15
15
 
16
16
  ---
17
17
 
@@ -19,9 +19,9 @@ Document, diagnose, and fix the described bug.
19
19
 
20
20
  Use these files for context (each is optional — if a file is missing, proceed and note the assumption you fell back on):
21
21
 
22
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology **and tracker-provider specifics** (which tracker, work-item types, commit-link syntax). If missing, default to `tracking_mode: internal` and track in `TODO.md`.
22
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology **and tracker-provider specifics** (which tracker, work-item types, commit-link syntax). If missing, default to `tracking_mode: internal` and track in `TODO.md`.
23
23
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect. If missing, proceed without ADR constraints.
24
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Coverage thresholds. If missing, match the test conventions already present in the repo.
24
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Coverage thresholds. If missing, match the test conventions already present in the repo.
25
25
 
26
26
  Workflow:
27
27
 
@@ -40,7 +40,7 @@ Workflow:
40
40
  2. **Record the bug** — file it in whatever tracker this repo uses. Resolve `tracking_mode` from `.arcane.json` (or the repo's feature/PRD frontmatter); if unset, **ask** rather than assuming.
41
41
 
42
42
  - **`tracking_mode: internal`** (or no tracker configured) — append the bug to `TODO.md` (create it if absent) using the captured fields from Step 1. Use the `TODO.md` entry's identifier as `{WORK_ITEM_ID}`. No external tooling required.
43
- - **`tracking_mode: external`** — file a work item in the configured provider. Read [governance/development-methodology.md](../../governance/development-methodology.md) for the provider, work-item type, and required fields; do **not** assume Azure DevOps. Extract the returned id as `{WORK_ITEM_ID}`.
43
+ - **`tracking_mode: external`** — file a work item in the configured provider. Read [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) for the provider, work-item type, and required fields; do **not** assume Azure DevOps. Extract the returned id as `{WORK_ITEM_ID}`.
44
44
 
45
45
  *Azure DevOps is one such provider — if and only if `.arcane.json` / methodology names it (and the `az` CLI is available), file it like so. Resolve `{ADO_ORG}` and `{ADO_PROJECT}` from `.arcane.json`; ask if unset:*
46
46
  ```bash
@@ -86,7 +86,7 @@ Workflow:
86
86
 
87
87
  {WORK_ITEM_LINK}
88
88
  ```
89
- Follow Conventional Commits format. For `{WORK_ITEM_LINK}`, use the commit-link convention your tracker expects (per [governance/development-methodology.md](../../governance/development-methodology.md)) — e.g. `Fixes AB#{WORK_ITEM_ID}` for Azure DevOps, `Fixes #{WORK_ITEM_ID}` for GitHub Issues, or a plain `Refs TODO.md` for internal mode. Wait for user approval before executing `git commit`.
89
+ Follow Conventional Commits format. For `{WORK_ITEM_LINK}`, use the commit-link convention your tracker expects (per [governance/development-methodology.md](../../.arcane/governance/development-methodology.md)) — e.g. `Fixes AB#{WORK_ITEM_ID}` for Azure DevOps, `Fixes #{WORK_ITEM_ID}` for GitHub Issues, or a plain `Refs TODO.md` for internal mode. Wait for user approval before executing `git commit`.
90
90
 
91
91
  8. **Close out the tracker** — update the work item's state to reflect the fix:
92
92
  - **`internal`** — mark the `TODO.md` entry as resolved (check it off / move to a Done section).
@@ -98,7 +98,7 @@ Workflow:
98
98
  --org https://dev.azure.com/{ADO_ORG} \
99
99
  --output json
100
100
  ```
101
- For other providers, follow [governance/development-methodology.md](../../governance/development-methodology.md).
101
+ For other providers, follow [governance/development-methodology.md](../../.arcane/governance/development-methodology.md).
102
102
 
103
103
  Rules:
104
104
  - Fix only the reported bug. Do not bundle unrelated improvements.
package/dist/assets/.github/prompts/spell-check-drift.prompt.md CHANGED
@@ -25,7 +25,7 @@ Use these files first:
25
25
  - [TODO.md](../../TODO.md)
26
26
  - [DECISIONS.md](../../DECISIONS.md)
27
27
  - [ai-context/system-prompt-context.md](../../ai-context/system-prompt-context.md)
28
- - [agents/agent-policies.md](../../agents/agent-policies.md)
28
+ - [agents/agent-policies.md](../../.arcane/governance/agent-policies.md)
29
29
  - Most recent journal file(s) in [journal/](../../journal/)
30
30
  - Relevant business overviews under [ventures/](../../ventures/)
31
31
 
package/dist/assets/.github/prompts/spell-close-session.prompt.md CHANGED
@@ -137,7 +137,7 @@ Rules:
137
137
  - Delete the local topic branch: `git branch -d <branch>`.
138
138
  - Verify `git log --oneline -3` shows the merged change at HEAD.
139
139
  - If stale local branches exist (merged or older than 7 days), list them and suggest cleanup.
140
- - See [governance/git-conventions.md](../../governance/git-conventions.md) Post-Merge Cleanup section.
140
+ - See [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) Post-Merge Cleanup section.
141
141
 
142
142
  11. **Return a concise closure report.**
143
143
 
package/dist/assets/.github/prompts/spell-commit-work.prompt.md CHANGED
@@ -19,7 +19,7 @@ Commit the current work in progress using Conventional Commits format.
19
19
 
20
20
  Use these files first:
21
21
 
22
- - [governance/git-conventions.md](../../governance/git-conventions.md) — Conventional Commits reference and agent attribution model
22
+ - [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) — Conventional Commits reference and agent attribution model
23
23
  - [DECISIONS.md](../../DECISIONS.md) — for ADR context if relevant
24
24
 
25
25
  Workflow:
@@ -50,7 +50,7 @@ Workflow:
50
50
  - Run the detected formatter, then `git add` the resulting changes so they are part of this commit.
51
51
  - **If no formatter is configured, skip this step gracefully** — do not install one and do not block the commit.
52
52
 
53
- 3. **Determine authorship and partition the batch** — who produced each changed file or inseparable change set? See [governance/git-conventions.md](../../governance/git-conventions.md) Agent Attribution Model section and ADR-028.
53
+ 3. **Determine authorship and partition the batch** — who produced each changed file or inseparable change set? See [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) Agent Attribution Model section and ADR-028.
54
54
  - **Invariant: one commit has exactly one author.** Changes spanning authors must be split into separate commits.
55
55
  - Partition changed files by author first. Step 4 then groups by concern within each author partition; concern grouping must never recombine authors.
56
56
  - **Human wrote it:** no `--author` override needed (uses global Git config)
@@ -71,17 +71,18 @@ Workflow:
71
71
  - **Wiki-link check:** For any new `.md` files being committed, verify each has at least one outbound `[[...]]` wiki-link connecting it to the knowledge graph. Orphaned docs (no outbound links) break Obsidian's graph view. If missing, add a `Related:` or `See also:` line before committing. See the CLAUDE.md wiki-link conventions for the correct format.
72
72
 
73
73
  4.5. **Resolve execution authority before any commit or merge command:**
74
- - Declare `interaction_context: interactive | autonomous`. VS Code chat, editor chat, Claude Code, and any live operator session are `interactive`; never infer `autonomous` from tool access.
75
- - Resolve the acting agent's effective power level and `exec_allowed` only through the EF-27 loader-validated roster and definition. Do not parse YAML directly or trust an unvalidated value.
76
- - If interaction context, consent provenance, roster identity, power level, or `exec_allowed` is missing/invalid/unavailable, fail closed to the least-authorized path. Print: `Authorization downgraded: <input> is <missing/invalid>. Human execution is required for <commit/merge>.`
77
- - `exec_allowed: false` always requires human execution, regardless of power level.
78
-
79
- | Context / validated authority | Commit | Merge / auto-complete |
80
- | --- | --- | --- |
81
- | Interactive, any power | Exact operator approval required | Separate exact operator approval **and** Magus+ required |
82
- | Autonomous, below Magus | May commit to topic branch when `exec_allowed` | Prohibited; queue PR for human completion |
83
- | Autonomous, Magus+ | May commit when `exec_allowed` | May self-merge within approved scope |
84
- | Missing or invalid authority | Human execution required | Human execution required |
74
+
75
+ - Declare `interaction_context: interactive | autonomous`. VS Code chat, editor chat, Claude Code, and any live operator session are `interactive`; never infer `autonomous` from tool access.
76
+ - Resolve the acting agent's effective power level and `exec_allowed` only through the EF-27 loader-validated roster and definition. Do not parse YAML directly or trust an unvalidated value.
77
+ - If interaction context, consent provenance, roster identity, power level, or `exec_allowed` is missing/invalid/unavailable, fail closed to the least-authorized path. Print: `Authorization downgraded: <input> is <missing/invalid>. Human execution is required for <commit/merge>.`
78
+ - `exec_allowed: false` always requires human execution, regardless of power level.
79
+
80
+ | Context / validated authority | Commit | Merge / auto-complete |
81
+ | ----------------------------- | ---------------------------------------------- | -------------------------------------------------------- |
82
+ | Interactive, any power | Exact operator approval required | Separate exact operator approval **and** Magus+ required |
83
+ | Autonomous, below Magus | May commit to topic branch when `exec_allowed` | Prohibited; queue PR for human completion |
84
+ | Autonomous, Magus+ | May commit when `exec_allowed` | May self-merge within approved scope |
85
+ | Missing or invalid authority | Human execution required | Human execution required |
85
86
 
86
87
  5. **Determine commit type** using Conventional Commits standard:
87
88
  - `feat` — new feature or capability
@@ -208,7 +209,7 @@ Workflow:
208
209
  - If branch is not attached to any active worktree, run `git branch -d <branch>`.
209
210
  - Return to `main` only when appropriate for the active session/worktree context.
210
211
  - If other stale local branches exist (merged or older than 7 days), list them and suggest cleanup.
211
- - See [governance/git-conventions.md](../../governance/git-conventions.md) Post-Merge Cleanup section.
212
+ - See [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) Post-Merge Cleanup section.
212
213
 
213
214
  ## Troubleshooting
214
215
 
package/dist/assets/.github/prompts/spell-enchant.prompt.md CHANGED
@@ -9,7 +9,7 @@ agent: agent
9
9
 
10
10
  - This spell takes an existing PRD and enchants it to production-grade quality.
11
11
  - It proactively identifies missing features, UX gaps, accessibility issues, performance targets, and security requirements that the original PRD didn't specify.
12
- - Applies two analytical lenses: a **research lens** (competitive analysis, industry standards) and a **marketing/brand lens** (brand, UX, first-impression review). In the default Arcane roster these map to the Alexander and Circe personas; other orgs map their own — see [agent-policies](../../agents/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md).
12
+ - Applies two analytical lenses: a **research lens** (competitive analysis, industry standards) and a **marketing/brand lens** (brand, UX, first-impression review). In the default Arcane roster these map to the Alexander and Circe personas; other orgs map their own — see [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md).
13
13
  - Output: Enhanced PRD with `[ENCHANTED]`-tagged additions, before/after quality scorecard, and research summaries.
14
14
  - Use this between `spell-plan` and `spell-architect` (or `spell-scope` for large PRDs). It **consumes** a drafted PRD and **feeds** an architecture/scoping spell; it does not author a PRD from scratch (that is `spell-plan`) nor implement one (`spell-implement`).
15
15
 
@@ -19,11 +19,11 @@ Enchant the provided PRD to exceptional quality.
19
19
 
20
20
  Use these files for context. All are optional — if a file is absent, fall back as noted and continue rather than aborting:
21
21
 
22
- - [governance/product-excellence-standards.md](../../governance/product-excellence-standards.md) — Quality dimensions, PRD Quality Scorecard, scoring rubric (Bronze / Silver / Gold). **If missing:** warn the user that the canonical scorecard was not found, then proceed with the embedded dimension list (Requirements Completeness, UX, Accessibility, Performance, Security, Responsive Design, Competitive Differentiation) and default to the **Public MVP** profile.
23
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology, story sizing rules. **If missing:** treat story sizing as advisory and proceed.
24
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage thresholds. **If missing:** omit framework-specific coverage targets from acceptance criteria.
22
+ - [governance/product-excellence-standards.md](../../.arcane/governance/product-excellence-standards.md) — Quality dimensions, PRD Quality Scorecard, scoring rubric (Bronze / Silver / Gold). **If missing:** warn the user that the canonical scorecard was not found, then proceed with the embedded dimension list (Requirements Completeness, UX, Accessibility, Performance, Security, Responsive Design, Competitive Differentiation) and default to the **Public MVP** profile.
23
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology, story sizing rules. **If missing:** treat story sizing as advisory and proceed.
24
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage thresholds. **If missing:** omit framework-specific coverage targets from acceptance criteria.
25
25
  - [security/threat-model.md](../../security/threat-model.md) — Active threat model. **If missing:** apply generic OWASP-style security baselines for the Security dimension.
26
- - [agents/agent-policies.md](../../agents/agent-policies.md) / [governance/naming-conventions.md](../../governance/naming-conventions.md) — Agent roster and persona naming. **If missing:** apply the two lenses (research, marketing/brand) without naming personas.
26
+ - [agents/agent-policies.md](../../.arcane/governance/agent-policies.md) / [governance/naming-conventions.md](../../.arcane/governance/naming-conventions.md) — Agent roster and persona naming. **If missing:** apply the two lenses (research, marketing/brand) without naming personas.
27
27
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect. **If missing:** assume no binding ADR constraints.
28
28
  - [project.md](../../project.md) — Project goals and business context. **If missing:** infer business context from the PRD itself and flag any assumptions.
29
29
 
@@ -42,7 +42,7 @@ Accept the PRD from one of these input sources:
42
42
  | **Tracker work item ID** | `#508` or `508` with a tracker reference | Respect `tracking_mode` and detect the provider (see below), then fetch the work item and extract its title, description, and acceptance criteria |
43
43
 
44
44
  If the input is a tracker work item ID:
45
- 1. **Determine tracking mode and provider.** Read `tracking_mode` (internal/external) from `.arcane.json` or PRD frontmatter, and detect the configured tracker provider rather than assuming one. The shared tracker-resolution rules live in [governance/development-methodology.md](../../governance/development-methodology.md) — follow them rather than hard-coding a single provider.
45
+ 1. **Determine tracking mode and provider.** Read `tracking_mode` (internal/external) from `.arcane.json` or PRD frontmatter, and detect the configured tracker provider rather than assuming one. The shared tracker-resolution rules live in [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — follow them rather than hard-coding a single provider.
46
46
  - For an **Azure DevOps** provider, fetch via `az boards work-item show --id {id} --org https://dev.azure.com/{ADO_ORG} --output json` and extract `System.Description`, `Microsoft.VSTS.Common.AcceptanceCriteria`, and `System.Title`. Resolve `{ADO_ORG}` (and `{ADO_PROJECT}` if needed) from `.arcane.json` or the PRD frontmatter; **if unset, ask the user** rather than assuming a default.
47
47
  - For other providers (e.g. a GitHub issue), use the provider's equivalent fetch and map title / body / acceptance-criteria fields accordingly.
48
48
  2. If the work item has child items, fetch those too — they may contain additional requirements.
@@ -93,7 +93,7 @@ For each dimension where the current score is **below the profile's target**, id
93
93
 
94
94
  ### 3. Research Phase (Research Lens)
95
95
 
96
- Apply the **research lens** (in the default Arcane roster this is the Alexander / Research & Backlog Analyst persona — see [agent-policies](../../agents/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md); other orgs map their own analyst). Conduct a thorough analysis:
96
+ Apply the **research lens** (in the default Arcane roster this is the Alexander / Research & Backlog Analyst persona — see [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md); other orgs map their own analyst). Conduct a thorough analysis:
97
97
 
98
98
  #### 3a. Competitive Analysis
99
99
  - Identify the top 3 alternatives/competitors for this type of app
@@ -143,7 +143,7 @@ Document findings as (the persona name below reflects the default roster; substi
143
143
 
144
144
  ### 4. Marketing & Brand Review (Marketing/Brand Lens)
145
145
 
146
- Apply the **marketing/brand lens** (in the default Arcane roster this is the Circe / Marketing Strategist persona — see [agent-policies](../../agents/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md); other orgs map their own strategist). Evaluate the PRD from a brand and user-perception perspective:
146
+ Apply the **marketing/brand lens** (in the default Arcane roster this is the Circe / Marketing Strategist persona — see [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md); other orgs map their own strategist). Evaluate the PRD from a brand and user-perception perspective:
147
147
 
148
148
  #### 4a. First Impressions
149
149
  - If a user saw this app for the first time with zero context, what would they think?
package/dist/assets/.github/prompts/spell-full-cycle.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This prompt chains all Spell Loop phases into a single autonomous pipeline.
11
11
  - Includes optional PRD enchantment (spell-enchant) between Plan and Architect for quality enhancement.
12
12
  - Only one human touchpoint: approving the PR at ship time.
13
- - Delegates each phase to the appropriate specialized agent role (research, architecture, build, QA, marketing review). Resolve concrete personas from [agent-policies](../../governance/agent-policies.md) / [naming-conventions](../../governance/naming-conventions.md); if neither is present, proceed with role names directly.
13
+ - Delegates each phase to the appropriate specialized agent role (research, architecture, build, QA, marketing review). Resolve concrete personas from [agent-policies](../../.arcane/governance/agent-policies.md) / [naming-conventions](../../.arcane/governance/naming-conventions.md); if neither is present, proceed with role names directly.
14
14
  - If any phase fails, the pipeline halts and reports the blocker — no silent failures.
15
15
 
16
16
  ---
@@ -19,13 +19,13 @@ Run the complete Spell Loop end-to-end for the described feature.
19
19
 
20
20
  Use these files for context:
21
21
 
22
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology and stories.json format
23
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage requirements
24
- - [governance/cicd-standards.md](../../governance/cicd-standards.md) — CI/CD pipeline and deployment gates
25
- - [governance/git-conventions.md](../../governance/git-conventions.md) — Branch discipline and commit format
22
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology and stories.json format
23
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage requirements
24
+ - [governance/cicd-standards.md](../../.arcane/governance/cicd-standards.md) — CI/CD pipeline and deployment gates
25
+ - [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) — Branch discipline and commit format
26
26
  - [project.md](../../project.md) — Project goals and priorities
27
27
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect
28
- - [governance/product-excellence-standards.md](../../governance/product-excellence-standards.md) — PRD Quality Scorecard for enchantment
28
+ - [governance/product-excellence-standards.md](../../.arcane/governance/product-excellence-standards.md) — PRD Quality Scorecard for enchantment
29
29
 
30
30
  ---
31
31
 
package/dist/assets/.github/prompts/spell-implement.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This is the core autonomous loop of the Spell Loop methodology.
11
11
  - Each iteration: pick a story → implement → run tests → commit if passing → update stories.json → loop.
12
12
  - Uses fresh context per iteration — only stories.json, progress.txt, and git history carry forward.
13
- - See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
13
+ - See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
14
14
 
15
15
  ---
16
16
 
@@ -18,8 +18,8 @@ Run the autonomous implementation loop for the current feature.
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology
22
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks and coverage requirements
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology
22
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks and coverage requirements
23
23
  - The feature's `architecture.md` — for tech decisions and patterns
24
24
  - The feature's `stories.json` — for the work breakdown
25
25
  - The feature's `progress.txt` (in `features/{slug}/`, if present) — accumulated learnings from prior iterations; read it before each iteration and append new learnings as the loop proceeds
package/dist/assets/.github/prompts/spell-open-session.prompt.md CHANGED
@@ -24,9 +24,9 @@ Use these files first:
24
24
  - [project.md](../../project.md)
25
25
  - [TODO.md](../../TODO.md)
26
26
  - [DECISIONS.md](../../DECISIONS.md)
27
- - [naming-conventions.md](../../naming-conventions.md)
27
+ - [naming-conventions.md](../../.arcane/governance/naming-conventions.md)
28
28
  - [ai-context/system-prompt-context.md](../../ai-context/system-prompt-context.md)
29
- - [agents/agent-policies.md](../../agents/agent-policies.md)
29
+ - [agents/agent-policies.md](../../.arcane/governance/agent-policies.md)
30
30
  - Most recent journal file(s) in [journal/](../../journal/)
31
31
  - Relevant business overview(s) under [ventures/](../../ventures/)
32
32
 
@@ -42,14 +42,14 @@ Check `ai-context/system-prompt-context.md` for a `## Next Session Handoff` sect
42
42
 
43
43
  Do not create a branch during a read-only session. Immediately before the first file edit, generated file, staging action, or other repository mutation, classify the current Git/remote state and apply exactly one path:
44
44
 
45
- | Observed state | Required action before mutation |
46
- | --- | --- |
47
- | Supported, authenticated GitHub/ADO remote + trunk checked out | Create and switch the **current worktree only** to `sessions/YYYY-MM-DD-<topic-slug>`, derived deterministically from the focus, handoff active task, or top next action. |
48
- | Already on a compliant `sessions/YYYY-MM-DD-<topic-slug>` branch | Stay on it; do not create or switch branches. |
49
- | Noncompliant unpushed branch with no active PR | Rename it to the deterministic session name before mutation. |
50
- | Branch has an active PR | Stay on the PR branch and report it; never rename a branch backing an active PR. |
51
- | Current path is a linked worktree | Mutate/switch only the current worktree. Never switch or delete a branch attached to another worktree. |
52
- | No remote, unsupported remote, or provider authentication unavailable | Stay on the repository trunk. Print `Local-only session: no usable remote merge path; mutations remain on <trunk> and close-session must use its local-only path.` |
45
+ | Observed state | Required action before mutation |
46
+ | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
47
+ | Supported, authenticated GitHub/ADO remote + trunk checked out | Create and switch the **current worktree only** to `sessions/YYYY-MM-DD-<topic-slug>`, derived deterministically from the focus, handoff active task, or top next action. |
48
+ | Already on a compliant `sessions/YYYY-MM-DD-<topic-slug>` branch | Stay on it; do not create or switch branches. |
49
+ | Noncompliant unpushed branch with no active PR | Rename it to the deterministic session name before mutation. |
50
+ | Branch has an active PR | Stay on the PR branch and report it; never rename a branch backing an active PR. |
51
+ | Current path is a linked worktree | Mutate/switch only the current worktree. Never switch or delete a branch attached to another worktree. |
52
+ | No remote, unsupported remote, or provider authentication unavailable | Stay on the repository trunk. Print `Local-only session: no usable remote merge path; mutations remain on <trunk> and close-session must use its local-only path.` |
53
53
 
54
54
  A usable merge path requires a configured remote on a supported provider (`github.com`, `dev.azure.com`, or `visualstudio.com`) and authenticated provider tooling. A remote URL alone is insufficient. Re-evaluate immediately before the first mutation so a remote added or removed during the read-only portion is handled from observed state.
55
55
 
@@ -82,7 +82,7 @@ Before anything else, check:
82
82
  - If missing, ask the operator to choose now. Default to `external` + `ado` only when existing ADO context already exists (backward compatibility).
83
83
  - **Open PRs (external/ado mode only):** if tracking mode is `external` with provider `ado` and ADO MCP is available, list all open PRs across all repos in the configured repo list (resolve from `.arcane.json`; if unset, ask the operator which repos to scan). Flag PRs older than 3 days as stale, older than 7 days as overdue. Format each as a clickable markdown link: `[PR #{id} — {title}](https://dev.azure.com/{ADO_ORG}/{ADO_PROJECT}/_git/{repo}/pullrequest/{id})` — resolve `{ADO_ORG}` and `{ADO_PROJECT}` from `.arcane.json` / PRD frontmatter; ask if unset. Never list a bare `PR #NNN`.
84
84
  - **Uncommitted changes:** Run `git status` and report any uncommitted files.
85
- - **Arcane version check (two-axis):** If `.arcane.json` exists in the repo root, check both whether the repo's managed files are behind the installed CLI *and* whether the installed CLI is behind the latest published version of `arcane-cli`:
85
+ - **Arcane version check (two-axis):** If `.arcane.json` exists in the repo root, check both whether the repo's managed files are behind the installed CLI _and_ whether the installed CLI is behind the latest published version of `arcane-cli`:
86
86
  - Read the installed version from `.arcane.json` (field: `arcaneVersion` or `version`).
87
87
  - Determine the version of the installed `arcane-cli` CLI (for example, `npx arcane-cli --version`, or the locally installed package version).
88
88
  - Run `npm view arcane-cli version` to get the latest published version.
package/dist/assets/.github/prompts/spell-plan.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This prompt generates a PRD.md from a feature description or TODO item.
11
11
  - It follows a structured analysis pattern — requirements, acceptance criteria, and constraints.
12
12
  - Output feeds directly into `spell-architect` as the next phase of the Spell Loop.
13
- - See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference.
13
+ - See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference.
14
14
 
15
15
  ---
16
16
 
@@ -18,7 +18,7 @@ Generate a Product Requirements Document for the described feature or initiative
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology
22
22
  - [project.md](../../project.md) — Project goals and priorities
23
23
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to respect
24
24
 
package/dist/assets/.github/prompts/spell-present-arcane.prompt.md CHANGED
@@ -5,7 +5,7 @@ argument-hint: '[summary|deck] + optional audience/size — e.g., "for investors
5
5
  agent: agent
6
6
  ---
7
7
 
8
- See [[governance/development-methodology|Development Methodology]] for full Spell Loop reference. Project context: [[project|Project Overview]].
8
+ See [[.arcane/governance/development-methodology|Development Methodology]] for full Spell Loop reference. Project context: [[project|Project Overview]].
9
9
 
10
10
  ## Mode Selection
11
11
 
@@ -39,10 +39,10 @@ Read these files before generating the presentation. They are the ground truth *
39
39
  | [project.md](../../project.md) | Mission, vision, core principles, entities, goals | `README.md`, then ask the operator for the mission |
40
40
  | [ai-context/system-prompt-context.md](../../ai-context/system-prompt-context.md) | Environment, agent stack, current state | Infer environment from repo; omit slide detail if unknown |
41
41
  | [DECISIONS.md](../../DECISIONS.md) | Key ADRs — decisions that shaped the architecture | Skip ADR callouts; note that decision records are absent |
42
- | [agents/agent-capability-matrix.md](../../agents/agent-capability-matrix.md) | Agent lineup and capability tiers | `.github/agents/*.agent.md`; else present the system generically |
43
- | [agents/agent-policies.md](../../agents/agent-policies.md) | Power levels, autonomy model | [[governance/naming-conventions]]; else describe roles generically |
42
+ | `.github/agents/*.agent.md` | Agent lineup and capability tiers | Present the system generically if no generated agent files exist |
43
+ | [agents/agent-policies.md](../../.arcane/governance/agent-policies.md) | Power levels, autonomy model | [[.arcane/governance/naming-conventions]]; else describe roles generically |
44
44
  | `{BUSINESS_ROOT}/<business>/overview.md` | Per-business status (repeat for each business found) | Enumerate `{BUSINESS_ROOT}/*`; if none, present Arcane without a ventures act |
45
- | [governance/development-methodology.md](../../governance/development-methodology.md) | The Spell Loop — development workflow | Describe the Spell Loop from the spell library filenames |
45
+ | [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) | The Spell Loop — development workflow | Describe the Spell Loop from the spell library filenames |
46
46
  | `{INFRA_DOC}` — hardware/infra inventory (e.g. `infrastructure/hardware-inventory.md`) | Hardware context for demo credibility | Detect any infra/hardware doc; else omit the infrastructure slide |
47
47
  | [README.md](../../README.md) | Repo structure overview | List top-level directories directly |
48
48
 
@@ -87,7 +87,7 @@ Read these files before generating the presentation. They are the ground truth *
87
87
 
88
88
  5. **Arcane — the operating system for AI-run businesses** — What the repo is, what it contains, how it's structured
89
89
  6. **Security model** — full-disk encryption, least privilege, no root, SecretRef, private network mesh — why security is non-negotiable for a production system
90
- 7. **The AI agent stack** — the gateway plus the agent lineup, power levels, and tool profiles. Populate the roster from the agent-capability-matrix / `.github/agents/*.agent.md` (see [[governance/agent-policies]] / [[governance/naming-conventions]]); name each `{AGENT_NAME}` with its role rather than assuming a fixed cast. If no roster files exist, describe agent *roles* (e.g. research, marketing, ops, dev) generically.
90
+ 7. **The AI agent stack** — the gateway plus the agent lineup, power levels, and tool profiles. Populate the roster from the agent-capability-matrix / `.github/agents/*.agent.md` (see [[.arcane/governance/agent-policies]] / [[.arcane/governance/naming-conventions]]); name each `{AGENT_NAME}` with its role rather than assuming a fixed cast. If no roster files exist, describe agent *roles* (e.g. research, marketing, ops, dev) generically.
91
91
  8. **The Spell Loop** — Arcane's development methodology: spell-plan → spell-architect → spell-implement → spell-ship
92
92
  9. **Multi-client AI governance** — Same rules enforced across every AI client the operator uses. Cite the relevant governance ADR if a decision record exists (resolve the ADR id from `DECISIONS.md`); otherwise state the principle without an id.
93
93
  10. **Ventures overview** — one line per business found under `{BUSINESS_ROOT}` (e.g. `{BUSINESS_NAME}` — launch-ready, `{BUSINESS_NAME}` — active dev), plus the idea pipeline. If none exist, replace with a roadmap slide.
package/dist/assets/.github/prompts/spell-product-review.prompt.md CHANGED
@@ -25,7 +25,7 @@ Use these files for context:
25
25
 
26
26
  - [project.md](../../project.md) — Business goals and priorities
27
27
  - The relevant business docs under `{BUSINESS_ROOT}/` — KPIs, metrics, and product strategy. **If `{BUSINESS_ROOT}` or these docs are missing, proceed with what `project.md` provides and flag the gap; if even `project.md` is absent, report "insufficient context to review" and list what is missing rather than inventing goals.**
28
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop context
28
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop context
29
29
 
30
30
  Workflow:
31
31
 
package/dist/assets/.github/prompts/spell-review.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This prompt performs an adversarial code review — "looks good" is not acceptable.
11
11
  - The reviewer must explicitly cover every lens — correctness, security, performance, tests, naming/clarity, architecture — and state "no issues" for any lens that is clean. There is no finding quota: zero findings is a valid outcome on a clean or small diff.
12
12
  - Checks architecture compliance, test coverage, security, and coding standards.
13
- - See [[governance/development-methodology|Development Methodology]] for the adversarial review pattern.
13
+ - See [[.arcane/governance/development-methodology|Development Methodology]] for the adversarial review pattern.
14
14
 
15
15
  ---
16
16
 
@@ -18,8 +18,8 @@ Perform an adversarial review of the specified code changes.
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Adversarial review requirements
22
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Coverage thresholds to validate
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Adversarial review requirements
22
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Coverage thresholds to validate
23
23
  - [DECISIONS.md](../../DECISIONS.md) — ADRs to check compliance against
24
24
  - [security/threat-model.md](../../security/threat-model.md) — Security controls to validate
25
25
  - The feature's `architecture.md` — tech decisions that code must follow
package/dist/assets/.github/prompts/spell-scope.prompt.md CHANGED
@@ -18,15 +18,15 @@ Analyze the provided PRD and produce a scoped execution plan.
18
18
 
19
19
  Use these files for context. Each is optional — if a file is missing, proceed with the stated fallback and note the gap in the output's Open Questions:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology, story sizing rules, and the canonical **ADO Hierarchy Rules**. *Fallback: if missing, use the default sizing of 4–8 right-sized stories per cycle described below and skip external-tracker hierarchy mapping.*
22
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Testing frameworks per stack. *Fallback: if missing, flag test strategy as an open question.*
23
- - [governance/cicd-standards.md](../../governance/cicd-standards.md) — Pipeline requirements. *Fallback: if missing, omit pipeline considerations.*
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology, story sizing rules, and the canonical **ADO Hierarchy Rules**. *Fallback: if missing, use the default sizing of 4–8 right-sized stories per cycle described below and skip external-tracker hierarchy mapping.*
22
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Testing frameworks per stack. *Fallback: if missing, flag test strategy as an open question.*
23
+ - [governance/cicd-standards.md](../../.arcane/governance/cicd-standards.md) — Pipeline requirements. *Fallback: if missing, omit pipeline considerations.*
24
24
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to check against. *Fallback: if missing, treat all architecture decisions as new candidates.*
25
25
  - [security/threat-model.md](../../security/threat-model.md) — Active threat model. *Fallback: if missing, apply OWASP Top 10 as the baseline.*
26
- - [agents/agent-policies.md](../../agents/agent-policies.md) — Agent roster, power levels, capabilities. *Fallback: if missing, assign work by role label (architecture, backend, frontend, mobile, QA, DevOps, research) instead of named personas.*
27
- - [naming-conventions.md](../../naming-conventions.md) — Agent roster and role-to-persona mapping. *Fallback: if missing, refer to roles by their generic label.*
26
+ - [agents/agent-policies.md](../../.arcane/governance/agent-policies.md) — Agent roster, power levels, capabilities. *Fallback: if missing, assign work by role label (architecture, backend, frontend, mobile, QA, DevOps, research) instead of named personas.*
27
+ - [naming-conventions.md](../../.arcane/governance/naming-conventions.md) — Agent roster and role-to-persona mapping. *Fallback: if missing, refer to roles by their generic label.*
28
28
  - [project.md](../../project.md) — Project goals and business context. *Fallback: if missing, derive context from the PRD itself.*
29
- - [governance/product-excellence-standards.md](../../governance/product-excellence-standards.md) — PRD Quality Scorecard and scoring rubric. *Fallback: if missing, skip the Quality Quick-Check (section 1.5) and note that it was skipped.*
29
+ - [governance/product-excellence-standards.md](../../.arcane/governance/product-excellence-standards.md) — PRD Quality Scorecard and scoring rubric. *Fallback: if missing, skip the Quality Quick-Check (section 1.5) and note that it was skipped.*
30
30
 
31
31
  > **Roster by reference.** This spell maps work to **roles** (architecture, backend, frontend, mobile, QA, DevOps, research, marketing). Resolve each role to a concrete agent persona via `agents/agent-policies.md` / `naming-conventions.md` at run time — do not assume a fixed set of persona names.
32
32
 
@@ -118,7 +118,7 @@ For each epic, define:
118
118
 
119
119
  Only applies when `tracking_mode=external`. Skip entirely for internal mode.
120
120
 
121
- Do **not** inline the work-item-type fallback order or the parent/child linkage rules here — they are the single source of truth in [governance/development-methodology.md](../../governance/development-methodology.md) → **Process-Template-Aware ADO Hierarchy Rules**. Detect the provider from `external_provider`, then apply those rules. *Fallback: if that doc is missing, record the tracker mapping as an Open Question and proceed without item-type assignment.*
121
+ Do **not** inline the work-item-type fallback order or the parent/child linkage rules here — they are the single source of truth in [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) → **Process-Template-Aware ADO Hierarchy Rules**. Detect the provider from `external_provider`, then apply those rules. *Fallback: if that doc is missing, record the tracker mapping as an Open Question and proceed without item-type assignment.*
122
122
 
123
123
  Scope-specific delta (the only thing this spell adds on top of those rules): each split **epic** maps to the **Epic-level** logical level — use the `Epic` work item type whenever the resolved provider/template offers it, and record the selected type per epic in `execution-plan.md`. All lower-level and linkage decisions defer to the governance rules above.
124
124
 
package/dist/assets/.github/prompts/spell-ship.prompt.md CHANGED
@@ -18,10 +18,10 @@ Run the ship workflow for the specified branch or PR.
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop phases
22
- - [governance/cicd-standards.md](../../governance/cicd-standards.md) — CI/CD pipeline requirements and deployment gates
23
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Coverage thresholds
24
- - [governance/git-conventions.md](../../governance/git-conventions.md) — Branch policies and merge strategy
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop phases
22
+ - [governance/cicd-standards.md](../../.arcane/governance/cicd-standards.md) — CI/CD pipeline requirements and deployment gates
23
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Coverage thresholds
24
+ - [governance/git-conventions.md](../../.arcane/governance/git-conventions.md) — Branch policies and merge strategy
25
25
 
26
26
  Workflow:
27
27
 
@@ -86,7 +86,7 @@ Workflow:
86
86
  7. **Request human approval** — present the ship report and wait for explicit approval.
87
87
 
88
88
  8. **Execute merge** (after approval):
89
- - Merge using the project's merge strategy as defined in [governance/git-conventions.md](../../governance/git-conventions.md). **Do NOT squash** — squash merges are prohibited because they collapse per-commit attribution. Prefer rebase and fast-forward.
89
+ - Merge using the project's merge strategy as defined in [governance/git-conventions.md](../../.arcane/governance/git-conventions.md). **Do NOT squash** — squash merges are prohibited because they collapse per-commit attribution. Prefer rebase and fast-forward.
90
90
  - Verify CI passes on the target branch post-merge.
91
91
  - Tag release if applicable.
92
92
 
package/dist/assets/.github/prompts/spell-suggest-feature.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This prompt captures feature suggestions discovered during smoke testing or regular use.
11
11
  - It creates a structured user story, assesses impact, and files a tracker item using whatever provider the repo is configured for (respects `tracking_mode`; ADO is one option, not an assumption).
12
12
  - Output is a tracked backlog item ready for future `spell-plan` invocation (or `spell-scope` for large, multi-feature suggestions).
13
- - See [[governance/development-methodology|Development Methodology]] for the full Spell Loop reference and tracker-provider specifics.
13
+ - See [[.arcane/governance/development-methodology|Development Methodology]] for the full Spell Loop reference and tracker-provider specifics.
14
14
 
15
15
  ---
16
16
 
@@ -18,7 +18,7 @@ Capture and document the described feature suggestion.
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop methodology
21
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop methodology
22
22
  - [project.md](../../project.md) — Project goals and priorities
23
23
  - [DECISIONS.md](../../DECISIONS.md) — Existing ADRs to check for overlap
24
24
  - [TODO.md](../../TODO.md) — Current backlog items
@@ -72,7 +72,7 @@ Workflow:
72
72
  Extract the work item ID from the response.
73
73
  - If `tracking_mode=internal`, skip external item creation and track in `TODO.md` only.
74
74
  - If `external_provider=jira` or `other`, add a TODO note for provider-specific automation and continue with `TODO.md` tracking.
75
- - The ADO command above is illustrative; for the authoritative per-provider creation steps and field mappings, see [[governance/development-methodology|Development Methodology]].
75
+ - The ADO command above is illustrative; for the authoritative per-provider creation steps and field mappings, see [[.arcane/governance/development-methodology|Development Methodology]].
76
76
 
77
77
  6. **Update backlog** — add a line to `TODO.md`:
78
78
  ```markdown
@@ -107,4 +107,4 @@ This spell sits at the front of the Spell Loop — it captures and tracks; it do
107
107
  - **Feeds into [[spell-scope|spell-scope]]** for large or multi-feature suggestions — if the impact assessment lands on **L** effort (or the idea spans several features), route it to `spell-scope` first to break it down before planning.
108
108
  - **Consumes from usage/testing** — there is no upstream spell; suggestions originate from smoke testing or regular use (e.g. while running `spell-test`).
109
109
 
110
- See [[governance/development-methodology|Development Methodology]] for the canonical Spell Loop hand-off flow.
110
+ See [[.arcane/governance/development-methodology|Development Methodology]] for the canonical Spell Loop hand-off flow.
package/dist/assets/.github/prompts/spell-test.prompt.md CHANGED
@@ -10,7 +10,7 @@ agent: agent
10
10
  - This prompt runs tests, validates coverage against thresholds, and generates evidence artifacts.
11
11
  - Used after `spell-implement` to verify quality before `spell-review`.
12
12
  - Enforces the testing standards from ADR-050 (80% line / 95% critical path coverage).
13
- - See [[governance/testing-standards|Testing Standards]] for framework details.
13
+ - See [[.arcane/governance/testing-standards|Testing Standards]] for framework details.
14
14
 
15
15
  ---
16
16
 
@@ -18,8 +18,8 @@ Run test suites and validate quality for the specified scope.
18
18
 
19
19
  Use these files for context:
20
20
 
21
- - [governance/testing-standards.md](../../governance/testing-standards.md) — Frameworks, thresholds, evidence requirements
22
- - [governance/development-methodology.md](../../governance/development-methodology.md) — Spell Loop context
21
+ - [governance/testing-standards.md](../../.arcane/governance/testing-standards.md) — Frameworks, thresholds, evidence requirements
22
+ - [governance/development-methodology.md](../../.arcane/governance/development-methodology.md) — Spell Loop context
23
23
  - The feature's `stories.json` — for acceptance criteria to validate
24
24
 
25
25
  Workflow: