refactor: new skill setup for plugin

Author: ivklgn

.claude/skills/verify-plugin-integrity/SKILL.md

@@ -56,7 +56,7 @@ If a local spec conflicts with an external official doc, the external doc is gro
 - Before opening a PR that touches plugin structure
 - When cross-host (Claude + Cursor + Codex) manifest consistency is in doubt
 - **Not** for test runs — use `/archcore:verify`
-- **Not** for Archcore document freshness vs code — use `/archcore:actualize`
+- **Not** for Archcore document freshness vs code — use `/archcore:audit --drift`
 
 ---
 
@@ -316,7 +316,7 @@ Light staleness check against `.archcore/plugin/component-registry.doc.md`:
 - Hook scripts in `bin/` match the registry's Hook Scripts table
 - Per-host config table (`.claude-plugin/plugin.json`, `.cursor-plugin/plugin.json`, `.codex-plugin/plugin.json`, `.mcp.json`, `.codex.mcp.json`, `hooks/hooks.json`, `hooks/cursor.hooks.json`, `hooks/codex.hooks.json`, `.agents/plugins/marketplace.json`) all exist
 
-This is a spot-check, not a full audit — for full staleness detection use `/archcore:actualize`.
+This is a spot-check, not a full audit — for full staleness detection use `/archcore:audit --drift`.
 
 ---
 

README.md

@@ -86,7 +86,7 @@ Both manifests (`.claude-plugin/plugin.json` and `.cursor-plugin/plugin.json`) l
 
 Install, open your project, and try these three prompts. Each shows a different side of what your agent can now do.
 
-_Empty repo? Run `/archcore:bootstrap` first to seed a stack rule, a run-the-app guide, and (optionally) imports from your existing CLAUDE.md / AGENTS.md / .cursorrules._
+_Empty repo? Run `/archcore:init` first to seed a stack rule, a run-the-app guide, and (optionally) imports from your existing CLAUDE.md / AGENTS.md / .cursorrules._
 
 **1. "Before I change anything in `src/auth/`, what rules and prior decisions apply here?"**
 Archcore loads the rules, ADRs, specs, and patterns tied to that path — grouped by type, ranked by specificity — before the agent edits code. Works the same way for a file, a directory, or a topic.
@@ -154,8 +154,8 @@ Two pieces work together:
 
 ## What ships in the box
 
-- **16 Skills** — 9 intent workflows, 6 multi-step tracks, 1 utility
-- **16 Codex slash commands** — thin command wrappers over the same skill workflows
+- **7 Skills** — 6 intent workflows (init, context, capture, decide, plan, audit) and help
+- **7 Codex slash commands** — thin command wrappers over the same skill workflows
 - **2 Agents** — a universal assistant and a read-only auditor
 - **Hooks** — session-start context loading, MCP-only write enforcement, post-mutation validation, cascade staleness detection
 
@@ -165,14 +165,12 @@ The plugin assumes the [Archcore CLI](https://docs.archcore.ai/cli/install/) is
 
 Describe what you want in plain English — Archcore routes it to the right skill and document flow. The command is a shortcut, not the interface.
 
+- **First-time onboarding** — `/archcore:init`
 - **Understand what applies before a change** — `/archcore:context`
 - **Document a module, component, or API** — `/archcore:capture`
-- **Record a finalized decision** — `/archcore:decide`
-- **Establish a team standard** — `/archcore:standard`
-- **Plan a feature end-to-end** — `/archcore:plan`
-- **Review documentation health (dashboard or `--deep` audit)** — `/archcore:review`
-- **Detect stale docs after code drift** — `/archcore:actualize`
-- **First-time onboarding** — `/archcore:bootstrap`
+- **Record a finalized decision** — `/archcore:decide` (optionally codified as rule + guide or formalized as spec + plan)
+- **Plan a feature end-to-end** — `/archcore:plan` (switch flows with `--track product|feature|sources|iso`)
+- **Documentation health** — `/archcore:audit` (dashboard, `--deep` audit, or `--drift` for staleness detection)
 - **Navigate the system** — `/archcore:help`
 
 ### Document types (18)
@@ -200,22 +198,27 @@ Archcore supports 18 document types. There are no standalone per-type skills; in
 | `task-type` | experience | Recurring task patterns with proven workflows        |
 | `cpat`      | experience | Before/after code pattern changes with scope         |
 
-Create documents through intent commands such as `/archcore:decide`, `/archcore:capture`, and `/archcore:plan`; use `/archcore:sources-track` or `/archcore:iso-track` for niche requirements cascades. For exact type-level control, call `mcp__archcore__create_document` directly with the matching `type` parameter.
+Create documents through intent commands such as `/archcore:decide`, `/archcore:capture`, and `/archcore:plan`; for niche requirements cascades use `/archcore:plan --track sources` or `--track iso`. For exact type-level control, call `mcp__archcore__create_document` directly with the matching `type` parameter.
 
-### Tracks (6)
+### Multi-document flows
 
-Tracks orchestrate multi-document flows. Each step builds on the previous one, with proper relations created automatically.
+Two intent commands chain documents automatically — `/archcore:plan` for requirements cascades and `/archcore:decide` for decision continuations.
 
-| Track                | Flow                                         | Use when                                               |
-| -------------------- | -------------------------------------------- | ------------------------------------------------------ |
-| `product-track`      | idea → prd → plan                  | Lightweight product flow — simple and fast             |
-| `sources-track`      | mrd → brd → urd                    | Discovery-focused — market, business, then user inputs |
-| `iso-track`          | brs → strs → syrs → srs       | Formal ISO 29148 cascade with traceability             |
-| `architecture-track` | adr → spec → plan                  | Design decisions flowing into implementation           |
-| `standard-track`     | adr → rule → guide                 | Decision → codified standard → instructions  |
-| `feature-track`      | prd → spec → plan → task-type | Full feature lifecycle                                 |
+**`/archcore:plan` tracks** — switch flow with `--track`:
 
-Invoke: `/archcore:product-track`, `/archcore:architecture-track`, etc.
+| Track                  | Flow                                         | Use when                                               |
+| ---------------------- | -------------------------------------------- | ------------------------------------------------------ |
+| `product` *(default)*  | idea → prd → plan                  | Lightweight product flow — simple and fast             |
+| `feature`              | prd → spec → plan → task-type | Full feature lifecycle with formal contract            |
+| `sources`              | mrd → brd → urd                    | Discovery-focused — market, business, user inputs      |
+| `iso`                  | brs → strs → syrs → srs       | Formal ISO 29148 cascade with traceability             |
+
+**`/archcore:decide` continuations** — offered after an ADR:
+
+| Continuation       | Chain                       | Use when                                          |
+| ------------------ | --------------------------- | ------------------------------------------------- |
+| Standard cascade   | adr → rule → guide | Decision → codified standard → instructions |
+| Architecture cascade | adr → spec → plan | Design decisions flowing into implementation       |
 
 ## Agents
 

agents/archcore-assistant.md

@@ -60,7 +60,7 @@ Focus your expertise on what MCP instructions do NOT provide:
 - **Elicitation**: what questions to ask before creating each document type
 - **Content composition**: how to structure rich content from user answers
 - **Disambiguation**: when to use ADR vs RFC, PRD vs MRD, rule vs guide
-- **Orchestration**: how to chain documents in tracks (product-track, sources-track, ISO cascade, etc.)
+- **Orchestration**: how to chain documents in plan tracks (product/feature/sources/iso flows under `/archcore:plan --track …`) and decide continuations (rule + guide, or spec + plan after an ADR)
 - **Relation patterns**: which relation types are typical for each document type
 
 # Working Guidelines

bin/check-cascade

@@ -59,6 +59,6 @@ rm -f /tmp/archcore_cascade_$$ 2>/dev/null
 DOC_SHORT=$(printf '%s' "$DOC_REL" | sed 's|.*/||; s|\..*\.md$||; s|-| |g')
 AFFECTED_LINES=$(printf '%s' "$AFFECTED" | tr '\n' ' ')
 
-archcore_hook_info "[Archcore Cascade] Updated \"${DOC_SHORT}\". Documents that may need review: ${AFFECTED_LINES}Run /archcore:actualize for detailed analysis."
+archcore_hook_info "[Archcore Cascade] Updated \"${DOC_SHORT}\". Documents that may need review: ${AFFECTED_LINES}Run /archcore:audit --drift for detailed analysis."
 
 exit 0

bin/check-staleness

@@ -71,7 +71,7 @@ if [ "$AFFECTED_COUNT" -gt 0 ]; then
   printf '[Archcore Staleness] %s source files changed since last documentation update.\n' "$CHANGED_COUNT"
   printf 'Potentially affected documents:\n'
   printf '%s' "$AFFECTED" | head -10
-  printf 'Run /archcore:actualize for detailed analysis.\n'
+  printf 'Run /archcore:audit --drift for detailed analysis.\n'
 
   # Touch the stamp so we don't re-warn for 24h.
   mkdir -p "$STAMP_DIR" 2>/dev/null || true

bin/session-start

@@ -60,7 +60,7 @@ _archcore_emit_info() {
 if [ ! -d ".archcore" ]; then
   _init_msg="[Archcore] no .archcore/ directory in this project yet. When the user asks for any Archcore operation (create ADR, audit docs, etc.), call mcp__archcore__init_project once to initialize, then proceed. Do NOT write to .archcore/ directly — hooks will block it."
   if [ "${ARCHCORE_HIDE_EMPTY_NUDGE:-}" != "1" ]; then
-    _init_msg="${_init_msg} After init, suggest the user run /archcore:bootstrap to seed initial content (stack rule, run-the-app guide, optional import of existing CLAUDE.md / AGENTS.md / .cursorrules). Skip with ARCHCORE_HIDE_EMPTY_NUDGE=1."
+    _init_msg="${_init_msg} After init, suggest the user run /archcore:init to seed initial content (stack rule, run-the-app guide, optional import of existing CLAUDE.md / AGENTS.md / .cursorrules). Skip with ARCHCORE_HIDE_EMPTY_NUDGE=1."
   fi
   _archcore_emit_info "$_init_msg"
   exit 0
@@ -74,7 +74,7 @@ printf '%s' "$ARCHCORE_RAW_STDIN" | archcore hooks "$ARCHCORE_HOST" session-star
 # never competes with the CLI hook's structured output for the same JSON slot.
 if [ "${ARCHCORE_HIDE_EMPTY_NUDGE:-}" != "1" ] && archcore_is_functionally_empty ".archcore"; then
   echo ""
-  echo "[Archcore] .archcore/ is empty. Run /archcore:bootstrap to seed a stack rule, a run-the-app guide, and (optionally) imports from existing agent-instruction files like CLAUDE.md or AGENTS.md. Skip with ARCHCORE_HIDE_EMPTY_NUDGE=1."
+  echo "[Archcore] .archcore/ is empty. Run /archcore:init to seed a stack rule, a run-the-app guide, and (optionally) imports from existing agent-instruction files like CLAUDE.md or AGENTS.md. Skip with ARCHCORE_HIDE_EMPTY_NUDGE=1."
 fi
 
 # Run staleness check (code-document drift detection)

commands/actualize.md

@@ -0,0 +1,15 @@
+---
+description: Audit Archcore documentation health; --deep for full audit, --drift for staleness.
+argument-hint: "[--deep] [--drift] [category, tag, or scope]"
+---
+
+# /archcore:audit
+
+## Arguments
+
+The user invoked this command with: $ARGUMENTS
+
+## Instructions
+
+Use the Archcore skill at `skills/audit/SKILL.md`.
+