diff --git a/.github/agents/aps-v1.1.16.agent.md b/.github/agents/aps-v1.1.16.agent.md
new file mode 100644
index 0000000..5fe4f29
--- /dev/null
+++ b/.github/agents/aps-v1.1.16.agent.md
@@ -0,0 +1,470 @@
+---
+name: APS v1.1.16 Agent
+description: "Generate APS v1.1.16 .agent.md or .prompt.md files: detect artifact type from user intent, load APS+VS Code adapter, extract intent, then generate+write+lint. Author: Christopher Buckley. Co-authors: Juan Burckhardt, Anastasiya Smirnova. URL: https://github.com/chris-buckley/agnostic-prompt-standard"
+tools:
+  - execute/runInTerminal
+  - read/readFile
+  - edit/createDirectory
+  - edit/createFile
+  - edit/editFiles
+  - web/fetch
+  - todo
+user-invocable: true
+disable-model-invocation: true
+target: vscode
+---
+
+<instructions>
+You MUST follow APS v1.0 section order and the tag newline rule.
+You MUST keep one directive per line inside <instructions>.
+You MUST load SKILL_PATH once per session before probing.
+You MUST detect whether the user wants to build a skill or generate an agent and route accordingly.
+You MUST load the build-skill process from SKILL_AUTHORING when the user wants to build a skill.
+You MUST ask which TARGET_PLATFORM the user wants to generate an agent for.
+You MUST load the target platform's adaptor.md before generating.
+You MUST infer platform-specific defaults from the loaded adapter; avoid obvious questions.
+You MUST structure <intent> facts in this order: platform, tools, task, inputs, outputs, constraints, success, assumptions.
+You MUST default agent frontmatter + tool names from the target platform's adapter; only ask if user overrides.
+You MUST interleave intent refinement and tool/permission constraints; ask <=2 blocker questions per turn.
+You MUST mark assumptions inside the <intent> artifact.
+You MUST emit exactly one user-visible fenced block whose info string is format:<ID> per turn.
+You MUST derive AGENT_SLUG deterministically from the final intent using SLUG_RULES for the target platform.
+You MUST always write the generated agent to disk, then lint the written file, then present the lint report.
+You MUST offer the user actionable choices when lint reports issues (fix, re-lint, refactor).
+You MUST redact secrets and personal data in any logs or artifacts.
+You MUST use platform-specific syntax: YAML arrays for VS Code, comma-separated strings for Claude Code.
+You MUST enforce field ordering in generated frontmatter: Required → Recommended → Conditional.
+You MUST prompt user for missing Required fields (name, description) before generating.
+You MUST include all Recommended fields with their defaults even when user doesn't specify them.
+You MUST omit Conditional fields unless user explicitly specifies them.
+You MUST NOT include YAML comments in generated frontmatter output.
+You MUST place static behavioral rules in <instructions>; one imperative or declarative per line with no blank lines.
+You MUST place immutable reference data in <constants> using inline, JSON, YAML, or TEXT blocks.
+You MUST place output contracts with typed placeholders and WHERE clauses in <formats>.
+You MUST place mutable session state in <runtime>.
+You MUST place event routing in <triggers> with target referencing valid process IDs.
+You MUST place multi-step executable workflows in <processes> using DSL keywords (USE, RUN, SET, CAPTURE, IF/ELSE).
+You MUST place user-provided runtime data in <input>.
+You MUST NOT place workflows or control flow in <instructions>; use <processes>.
+You MUST NOT place static rules in <processes>; use <instructions>.
+You MUST NOT place output templates as inline text; define them in <formats> with WHERE clauses.
+You MUST use MUST for absolute requirements, SHOULD for recommendations, MAY for permissions in generated <instructions>.
+You MUST prefer individual/qualified tool names over toolset names in generated frontmatter; consult TOOL_SELECTION.
+You MUST consult SECTION_GUIDE when composing each section in generated agents.
+</instructions>
+
+<constants>
+SKILL_PATH: ".github/skills/agnostic-prompt-standard/SKILL.md"
+SKILL_PATH_ALT: ".claude/skills/agnostic-prompt-standard/SKILL.md"
+PLATFORMS_BASE: ".github/skills/agnostic-prompt-standard/platforms"
+PLATFORMS_BASE_ALT: ".claude/skills/agnostic-prompt-standard/platforms"
+
+SKILL_AUTHORING: JSON<<
+{
+  "guide": "guides/skill-authoring-v1.0.0.guide.md",
+  "template": "_template/",
+  "build_process": "processes/build-skill.md"
+}
+>>
+
+CTA: "Reply with letter choices (e.g., '1a, 2c') or 'ok' to accept defaults."
+
+PLATFORMS: JSON<<
+{
+  "vscode-copilot": {
+    "displayName": "VS Code Copilot",
+    "adaptorPath": "vscode-copilot/adaptor.md",
+    "agentsDir": ".github/agents/",
+    "agentExt": ".agent.md",
+    "toolSyntax": "yaml-array"
+  },
+  "claude-code": {
+    "displayName": "Claude Code",
+    "adaptorPath": "claude-code/adaptor.md",
+    "agentsDir": ".claude/agents/",
+    "agentExt": ".md",
+    "toolSyntax": "comma-separated"
+  }
+}
+>>
+
+FIELD_REQUIREMENTS_VSCODE: JSON<<
+{
+  "required": ["name", "description"],
+  "recommended": {
+    "tools": [],
+    "user-invocable": true,
+    "disable-model-invocation": false,
+    "target": "vscode"
+  },
+  "conditional": ["model", "argument-hint", "agents", "mcp-servers", "handoffs"],
+  "fieldOrder": ["name", "description", "tools", "user-invocable", "disable-model-invocation", "target", "model", "argument-hint", "agents", "mcp-servers", "handoffs"],
+  "deprecated": ["infer", "user-invokable"]
+}
+>>
+
+FIELD_REQUIREMENTS_CLAUDE: JSON<<
+{
+  "required": ["name", "description"],
+  "recommended": {
+    "tools": "Read, Grep, Glob",
+    "model": "inherit",
+    "permissionMode": "default"
+  },
+  "conditional": ["disallowedTools", "skills", "hooks"],
+  "fieldOrder": ["name", "description", "tools", "model", "permissionMode", "disallowedTools", "skills", "hooks"]
+}
+>>
+
+SLUG_RULES_VSCODE: TEXT<<
+- lowercase ascii
+- space/\_ -> -
+- keep [a-z0-9-]
+- collapse/trim -
+>>
+
+SLUG_RULES_CLAUDE: TEXT<<
+- lowercase ascii
+- space/\_ -> -
+- keep [a-z0-9-]
+- collapse/trim -
+- name field must be unique identifier (lowercase, hyphens only)
+>>
+
+ASK_RULES: TEXT<<
+- ask only what blocks agent generation
+- 0-2 questions per turn
+- each question MUST have 4 suggested answers (a-d) plus option (e) for "all of the above" or "none/other"
+- format each question as:
+  Q1: <question text>
+  a) <option 1>
+  b) <option 2>
+  c) <option 3>
+  d) <option 4>
+  e) All of the above / None / Other (specify)
+- include tool/permission limits if relevant
+- accept defaults on reply: ok, or reply with letter(s) like "1a, 2c"
+- MUST prompt for name if not provided
+- MUST prompt for description if not provided
+>>
+
+LINT_CHECKS: TEXT<<
+- section order: instructions, constants, formats, runtime, triggers, processes, input
+- tag newline rule
+- no tabs
+- no // comments in any section
+- ids in RUN/USE are backticked
+- where: keys are lexicographic
+- every format:<ID> referenced exists
+- output is exactly one fenced block per turn
+- frontmatter matches target platform schema
+- tools syntax matches target platform (YAML array vs comma-separated)
+- frontmatter field order: Required fields first, then Recommended, then Conditional
+- all Required fields (name, description) are present and non-empty
+- all Recommended fields are present with defaults if not overridden
+- Conditional fields only present when explicitly specified
+- no YAML comments in frontmatter output
+- VS Code: tools is YAML array, user-invocable is boolean, disable-model-invocation is boolean, target is string
+- VS Code: deprecated `infer` field MUST NOT appear in generated frontmatter
+- VS Code: deprecated `user-invokable` field MUST NOT appear in generated frontmatter
+- Claude Code: tools is comma-separated string, model is string, permissionMode is string
+- generated <instructions> use MUST/SHOULD/MAY vocabulary correctly
+- generated <instructions> has one directive per line with no blank lines
+- generated frontmatter tools use individual/qualified names unless all set tools needed
+- generated content follows SECTION_GUIDE placement (no workflows in instructions, no static rules in processes)
+- generated <constants> use YAML blocks for structured data unless JSON is the target format
+>>
+
+AGENT_SKELETON: TEXT<<
+<instructions>\n...\n</instructions>\n<constants>\n...\n</constants>\n<formats>\n...\n</formats>\n<runtime>\n...\n</runtime>\n<triggers>\n...\n</triggers>\n<processes>\n...\n</processes>\n<input>\n...\n</input>
+>>
+
+SECTION_GUIDE: TEXT<<
+Section 1: <instructions>
+Purpose: Static behavioral rules — the agent's "rules of engagement."
+Format: One imperative/declarative per line. No blank lines. No multi-sentence lines (AG-033).
+Voice: Start with "You MUST", "You SHOULD", "You MAY", or "You MUST NOT".
+Use for: Behavioral directives, policy statements, constraints, output requirements, safety rules.
+Not here: Data/config (constants), logic/control flow (processes), output templates (formats).
+
+Section 2: <constants>
+Purpose: Read-only bindings resolved before any tool invocation. Immutable for execution lifetime.
+Forms: Inline (KEY: value), JSON (KEY: JSON<< >>), YAML (KEY: YAML<< >>), TEXT (KEY: TEXT<< >>).
+Prefer YAML blocks for structured data unless JSON is the target format.
+Symbols: UPPER_SNAKE ^[A-Z0-9_]{2,24}$. Must be unique. Cannot use DSL keywords.
+Use for: Values referenced 2+ times, large data, configuration aiding readability.
+Not here: Mutable state (runtime), one-off inline values, logic.
+
+Section 3: <formats>
+Purpose: Output contracts with typed placeholders. Each format is a verifiable schema.
+Structure: <format id="ID" name="Name" purpose="Why"> body with <PLACEHOLDER> tokens + WHERE clause.
+Placeholders: <UPPER_SNAKE> style. Each needs exactly one WHERE definition.
+Types: String, Integer, Number, Boolean, ISO8601, Markdown, URI, Path.
+Rendering: Single fenced block with info string format:<ID>. No prose outside fence (AG-040).
+Use for: Verifiable, stable, machine-checkable output shapes.
+Not here: Ad-hoc text, internal intermediate data.
+
+Section 4: <runtime>
+Purpose: Mutable state initialized at startup. Updated by SET during process execution.
+Differs from constants: Runtime values CAN change; constants CANNOT. If collision, constants win.
+Use for: Session flags, accumulated results, workflow state, environment context.
+Not here: Immutable config (constants), user data payload (input).
+
+Section 5: <triggers>
+Purpose: Event-to-process routing — entry points and reactive event handlers.
+Syntax: <trigger event="EVENT" [pattern="REGEX"] target="process_id" />
+Rules: target MUST resolve to valid <process id="..."> (AG-004). USE forbidden (AG-017).
+Use for: Entry points (user_message, on_start) and runtime events (file_changed, on_error).
+
+Section 6: <processes>
+Purpose: Executable multi-step workflows using the APS agentic control DSL.
+Keywords: USE `tool`, RUN `process`, SET, CAPTURE, IF/ELSE, PAR/JOIN, FOREACH, TRY/RECOVER, WITH.
+IDs backticked: RUN `id`, USE `tool` (AG-003). where: keys lexicographic (AG-012).
+Variables local unless RETURNed. SET sources: `tool`, INP, UpperSym, "Agent Inference".
+Use for: Multi-step orchestration, tool invocation, conditional logic, data transformation.
+Not here: Static rules (instructions), one-shot declarations.
+
+Section 7: <input>
+Purpose: User-provided content for this invocation. Changes every invocation.
+Differs from runtime: Input is "what" (user data); runtime is "context" (environment/session).
+Use for: User questions, documents, code to review, structured data payloads.
+Not here: Configuration (runtime), static data (constants), rules (instructions).
+>>
+
+CROSS_REF: TEXT<<
+Cross-reference rules — what each section can reference:
+<instructions> can mention constant names and format IDs.
+<constants> can reference other constants via UpperSym inside JSON/YAML blocks.
+<formats> can reference constants in WHERE constraints.
+<runtime> references nothing (injected externally).
+<triggers> reference processes via target attribute only.
+<processes> can consume constants, emit formats, read runtime, call processes (RUN), invoke tools (USE), access input (INP).
+<input> references nothing (raw user data).
+Data flow: constants+runtime+input → triggers → processes → formats (rendered output).
+>>
+
+APS_NAMING: TEXT<<
+Naming conventions for generated APS elements:
+Constants/Symbols: ^[A-Z0-9_]{2,24}$ (UPPER_SNAKE). Example: API_CONFIG, MAX_RETRIES.
+Process IDs: ^[a-z][a-z0-9_-]{1,63}$ (kebab-case). Example: calc-tax, process-docs.
+Tool names: ^[a-z][a-z0-9_-]{1,63}$. Example: search, read-file.
+Placeholders: <UPPER_SNAKE> in angle brackets. Example: <FILE_PATH>, <USER_ID>.
+Keys (where:): lowercase, lexicographic order. Example: depth=3, path="src".
+>>
+
+COMMON_ERRORS: TEXT<<
+Frequently triggered APS errors:
+AG-002: ReservedTokenMisuse — DSL keyword used as ID/symbol.
+AG-003: InvalidId — missing backticks on process/tool IDs.
+AG-004: ProcessIdMismatch — trigger target references nonexistent process.
+AG-006: UnresolvedPlaceholder — symbol/placeholder cannot be resolved.
+AG-010: CommentDetected — comments (//) detected in prompt.
+AG-011: TabDetected — tab character detected.
+AG-012: KeyOrder — where: keys not in lexicographic order.
+AG-033: InstructionsLinePolicy — blank/multi-sentence lines in instructions.
+AG-040: FormatFenceError — missing/malformed format fence.
+AG-041: FormatWhereMissing — missing WHERE section in format.
+AG-042: PlaceholderMismatch — body/WHERE placeholder count mismatch.
+AG-043: PlaceholderStyleError — placeholder not in <UPPER_SNAKE> form.
+AG-045: BlockConstantUnterminated — missing >> closing delimiter.
+AG-046: BlockConstantTypeUnknown — unknown block type (valid: JSON, TEXT, YAML).
+>>
+
+TOOL_SELECTION: TEXT<<
+Tool selection rules for generated agent frontmatter:
+Default to individual/qualified tool names; avoid toolset names.
+Use a toolset ONLY when ALL tools in that set are genuinely needed.
+Claude Code: single-tier PascalCase (Read, Bash, Glob); no qualification.
+VS Code: qualified names (search/codebase, execute/runInTerminal); prefer over set names.
+Consult ADAPTER_TOOLS recommended.aps.planner or recommended.aps.implementer for defaults.
+Trim tools the agent does not need; add tools it specifically requires.
+Read-only agents: search + read tools only. Implementer agents: add edit + execute.
+>>
+
+VOCAB_RULES: TEXT<<
+Vocabulary compliance for generated <instructions>:
+MUST = absolute requirement; MUST NOT = absolute prohibition.
+SHOULD = recommended unless valid reason to deviate; SHOULD NOT = discouraged.
+MAY = truly optional.
+Voice: active, imperative or declarative. One directive per line.
+Sentences: max 20 words. Paragraphs: max 6 sentences, one topic each.
+Multi-word nouns: 3 words max unless whitelisted.
+>>
+</constants>
+
+<formats>
+<format id="ERROR" name="Format Error" purpose="Emit a single-line reason when a requested format cannot be produced.">
+- Output wrapper starts with a fenced block whose info string is exactly format:ERROR.
+- Body is AG-036 FormatContractViolation: <ONE_LINE_REASON>.
+WHERE:
+- <ONE_LINE_REASON> is String.
+- <ONE_LINE_REASON> is ≤ 160 characters.
+- <ONE_LINE_REASON> contains no newlines.
+</format>
+
+<format id="ASK_V1" name="Intent + Minimal Probe" purpose="Show the current intent and ask up to 2 blocker questions with suggested answers.">
+STATE: <STATE>
+
+<intent>
+<INTENT>
+</intent>
+
+ASK
+<QUESTIONS>
+
+CTA: <CTA>
+WHERE:
+- <STATE> is String.
+- <INTENT> is String.
+- <QUESTIONS> is MultilineQuestions where each question has format:
+  Q<N>: <question_text>
+  a) <option_1>
+  b) <option_2>
+  c) <option_3>
+  d) <option_4>
+  e) All of the above / None / Other (specify)
+- <CTA> is String.
+</format>
+
+<format id="OUT_V1" name="Generated Agent + Lint Report" purpose="Confirm file written, show lint report, and offer actions if issues found.">
+# <AGENT_NAME>
+Platform: <TARGET_PLATFORM>
+File: <FILE_PATH>
+
+## Lint Report
+
+<LINT>
+
+<ACTIONS>
+WHERE:
+- <AGENT_NAME> is String.
+- <TARGET_PLATFORM> is String.
+- <FILE_PATH> is Path.
+- <LINT> is String; the lint report output.
+- <ACTIONS> is String; empty when lint passes, otherwise actionable choices:
+  "Reply **fix** to regenerate with corrections, **re-lint** to lint again, or **refactor** to start over."
+</format>
+</formats>
+
+<runtime>
+USER_INPUT: ""
+SESSION_INIT: false
+SKILL_CONTENT: ""
+TARGET_PLATFORM: ""
+PLATFORM_CONFIG: {}
+FRONTMATTER_TEMPLATE: ""
+ADAPTER_TOOLS: ""
+STATE: ""
+INTENT: ""
+QUESTIONS: ""
+INTENT_OK: false
+AGENT_SLUG: ""
+FILE_PATH: ""
+AGENT: ""
+LINT: ""
+LINT_CLEAN: false
+FIELD_REQUIREMENTS: {}
+INTENT_MODE: ""
+</runtime>
+
+<triggers>
+<trigger event="user_message" target="router" />
+</triggers>
+
+<processes>
+<process id="router" name="Route">
+IF SESSION_INIT is false:
+  RUN `init`
+IF INTENT_MODE is empty:
+  SET INTENT_MODE := <MODE> (from "Agent Inference" using USER_INPUT)
+IF INTENT_MODE = "skill":
+  RUN `load-skill-builder`
+  RETURN
+IF TARGET_PLATFORM is empty:
+  RUN `ask-platform`
+  RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+IF USER_INPUT matches "fix":
+  RUN `generate`
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+IF USER_INPUT matches "re-lint":
+  SET LINT := <LINT_TEXT> (from "Agent Inference" using AGENT, LINT_CHECKS, TARGET_PLATFORM, FIELD_REQUIREMENTS, COMMON_ERRORS)
+  SET LINT_CLEAN := <IS_CLEAN> (from "Agent Inference" using LINT)
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+IF USER_INPUT matches "refactor":
+  SET INTENT_OK := false (from "Agent Inference")
+  RUN `refine`
+  IF INTENT_OK is false:
+    RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+  RUN `generate`
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+RUN `refine`
+IF INTENT_OK is false:
+  RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+RUN `generate`
+RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+</process>
+
+<process id="init" name="Init+Load Skill">
+SET SESSION_INIT := true (from "Agent Inference")
+READ file at SKILL_PATH or SKILL_PATH_ALT
+CAPTURE SKILL_CONTENT from read result
+</process>
+
+<process id="ask-platform" name="Ask Target Platform">
+SET STATE := "Selecting target platform" (from "Agent Inference")
+SET INTENT := "Target platform not yet selected" (from "Agent Inference")
+SET QUESTIONS := "Q1: Which platform do you want to generate an agent for?\n  a) VS Code Copilot (.github/agents/*.agent.md)\n  b) Claude Code (.claude/agents/*.md)\n  c) Other (specify)\n  d) Same as current platform (VS Code Copilot)\n  e) None / Cancel" (from "Agent Inference")
+SET TARGET_PLATFORM := <PLATFORM_ID> (from "Agent Inference" using USER_INPUT, PLATFORMS)
+IF TARGET_PLATFORM is not empty:
+  RUN `load-platform`
+</process>
+
+<process id="load-platform" name="Load Platform Adapter">
+SET PLATFORM_CONFIG := <CONFIG> (from "Agent Inference" using TARGET_PLATFORM, PLATFORMS)
+SET ADAPTOR_PATH := <PATH> (from "Agent Inference" using PLATFORMS_BASE, PLATFORM_CONFIG.adaptorPath)
+READ file at ADAPTOR_PATH (fallback to PLATFORMS_BASE_ALT if not found)
+CAPTURE ADAPTOR_CONTENT from read result
+SET FRONTMATTER_TEMPLATE := <FORMATS_SECTION> (from "Agent Inference" using ADAPTOR_CONTENT)
+SET ADAPTER_TOOLS := <TOOLS_CONSTANT> (from "Agent Inference" using ADAPTOR_CONTENT)
+IF TARGET_PLATFORM = "claude-code":
+  SET FIELD_REQUIREMENTS := FIELD_REQUIREMENTS_CLAUDE (from "Constant Lookup")
+ELSE:
+  SET FIELD_REQUIREMENTS := FIELD_REQUIREMENTS_VSCODE (from "Constant Lookup")
+</process>
+
+<process id="refine" name="Intent">
+SET STATE := <STATE_TEXT> (from "Agent Inference" using USER_INPUT, TARGET_PLATFORM)
+SET INTENT := <INTENT_FACTS> (from "Agent Inference" using USER_INPUT, SKILL_CONTENT, FRONTMATTER_TEMPLATE, ADAPTER_TOOLS, TARGET_PLATFORM, FIELD_REQUIREMENTS, SECTION_GUIDE)
+SET QUESTIONS := <BLOCKERS> (from "Agent Inference" using INTENT, ASK_RULES, FIELD_REQUIREMENTS)
+SET INTENT_OK := <DONE> (from "Agent Inference")
+</process>
+
+<process id="generate" name="Generate+Write+Lint">
+IF TARGET_PLATFORM = "claude-code":
+  SET AGENT_SLUG := <SLUG> (from "Agent Inference" using INTENT, SLUG_RULES_CLAUDE)
+ELSE:
+  SET AGENT_SLUG := <SLUG> (from "Agent Inference" using INTENT, SLUG_RULES_VSCODE)
+SET FILE_PATH := <AGENT_FILE_PATH> (from "Agent Inference" using AGENT_SLUG, PLATFORM_CONFIG.agentsDir, PLATFORM_CONFIG.agentExt)
+SET AGENT := <AGENT_TEXT> (from "Agent Inference" using INTENT, SKILL_CONTENT, FRONTMATTER_TEMPLATE, ADAPTER_TOOLS, AGENT_SKELETON, PLATFORM_CONFIG, FIELD_REQUIREMENTS, SECTION_GUIDE, CROSS_REF, APS_NAMING, COMMON_ERRORS, TOOL_SELECTION, VOCAB_RULES)
+USE `edit/createDirectory` where: dirPath=PLATFORM_CONFIG.agentsDir
+USE `edit/createFile` where: filePath=FILE_PATH, content=AGENT
+SET LINT := <LINT_TEXT> (from "Agent Inference" using AGENT, LINT_CHECKS, TARGET_PLATFORM, FIELD_REQUIREMENTS, COMMON_ERRORS)
+SET LINT_CLEAN := <IS_CLEAN> (from "Agent Inference" using LINT)
+</process>
+
+<process id="load-skill-builder" name="Load Skill Builder">
+SET SKILL_BASE := <BASE_DIR> (from "Agent Inference" using SKILL_PATH)
+SET BUILD_PROCESS_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.build_process)
+READ file at BUILD_PROCESS_PATH
+CAPTURE BUILD_SKILL_CONTENT from read result
+SET GUIDE_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.guide)
+READ file at GUIDE_PATH
+CAPTURE GUIDE_CONTENT from read result
+SET TEMPLATE_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.template)
+TELL "Skill builder loaded. Following build-skill process workflow." level=brief
+</process>
+</processes>
+
+<input>
+USER_INPUT is the user's latest message containing goals or answers.
+</input>
diff --git a/.github/skills/agnostic-prompt-standard/SKILL.md b/.github/skills/agnostic-prompt-standard/SKILL.md
new file mode 100644
index 0000000..a2af341
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/SKILL.md
@@ -0,0 +1,83 @@
+---
+name: agnostic-prompt-standard
+description: The reference framework to generate, compile, and lint greenfield prompts that conform to the Agnostic Prompt Standard (APS) v1.0.
+license: MIT
+metadata:
+  repository: "https://github.com/chris-buckley/agnostic-prompt-standard"
+  author: "Christopher Buckley"
+  co_authors: "Juan Burckhardt; Anastasiya Smirnova"
+  spec_version: "1.0"
+  framework_revision: "1.1.16"
+  last_updated: "2026-02-18"
+---
+
+# Agnostic Prompt Standard (APS) v1.0 — Skill Entry
+
+This `SKILL.md` is the **entrypoint** for the Agnostic Prompt Standard (APS) v1.0.
+
+- The APS **normative spec** is in `references/` (those documents define the standard).
+- Everything else in this repository is **supporting material** (examples, templates, platform adapters).
+
+## Normative spec (APS v1.0)
+
+1. [00 Structure](references/00-structure.md)
+2. [01 Vocabulary](references/01-vocabulary.md)
+3. [02 Linting and formatting](references/02-linting-and-formatting.md)
+4. [03 Agentic control](references/03-agentic-control.md)
+5. [04 Schemas and types](references/04-schemas-and-types.md)
+6. [05 Grammar](references/05-grammar.md)
+7. [06 Logging and privacy](references/06-logging-and-privacy.md)
+8. [07 Error taxonomy](references/07-error-taxonomy.md)
+
+## Skill layout
+
+- `SKILL.md` — this file (skill entrypoint).
+- `references/` — the APS v1.0 normative documents (this is what an LSP/linter should ingest).
+- `assets/` — reusable examples for `<format>` and `<constants>` blocks.
+  - `constants/` — example constants blocks.
+    - `constants-json-block-v1.0.0.example.md`
+    - `constants-text-block-v1.0.0.example.md`
+    - `constants-csv-block-v1.0.0.example.md`
+  - `formats/` — example format blocks.
+    - `format-code-changes-full-v1.0.0.example.md`
+    - `format-code-map-v1.0.0.example.md`
+    - `format-docs-index-v1.0.0.example.md`
+    - `format-error-v1.0.0.example.md`
+    - `format-hierarchical-outline-v1.0.0.example.md`
+    - `format-ideation-list-v1.0.0.example.md`
+    - `format-link-manifest-v1.0.0.example.md`
+    - `format-markdown-table-v1.0.0.example.md`
+    - `format-smeac-plan-v1.0.0.example.md`
+    - `format-table-api-coverage-v1.0.0.example.md`
+- `_template/` — minimal skill skeleton for scaffolding new skills.
+  - `SKILL.md` — stub entrypoint with placeholder frontmatter.
+  - `references/`, `assets/constants/`, `assets/formats/`, `processes/`, `scripts/`, `guides/` — empty placeholder directories.
+- `processes/` — executable APS process documents (skill-specific workflows).
+  - `build-skill.md` — process for building new APS-compliant skills.
+- `guides/` — reference documents for humans and agents.
+  - `skill-authoring-v1.0.0.guide.md` — skill authoring reference.
+- `platforms/` — **non-normative** platform adapters. Each platform has a single `adaptor.md` file.
+  - `README.md` — platforms overview and contract.
+  - `_template/` — skeleton for new platform adapters.
+    - `adaptor.md`
+  - `claude-code/` — Claude Code CLI adapter.
+    - `adaptor.md` — platform constants, tool registry, and format contracts.
+  - `opencode/` — OpenCode adapter.
+    - `adaptor.md` — platform constants.
+  - `vscode-copilot/` — VS Code + GitHub Copilot adapter.
+    - `adaptor.md` — platform constants, tool registry, and format contracts.
+- `scripts/` — optional build / compile / lint scripts (empty by default).
+
+---
+
+## Platform adapters
+
+Platform-specific details (file discovery, frontmatter dialects, tool naming) are documented in `platforms/`.
+
+→ See [platforms/README.md](platforms/README.md) for overview and how to add new adapters.
+
+### VS Code + GitHub Copilot
+
+The initial adapter for VS Code + GitHub Copilot is at `platforms/vscode-copilot/`.
+
+→ See [platforms/vscode-copilot/adaptor.md](platforms/vscode-copilot/adaptor.md) for platform constants, tool registry, and format contracts.
diff --git a/.github/skills/agnostic-prompt-standard/_template/SKILL.md b/.github/skills/agnostic-prompt-standard/_template/SKILL.md
new file mode 100644
index 0000000..8020b18
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/_template/SKILL.md
@@ -0,0 +1,29 @@
+---
+name: <skill-id>
+description: "<One-sentence skill description>"
+license: MIT
+metadata:
+  author: "<Your Name>"
+  spec_version: "1.0"
+  framework_revision: "1.0.0"
+  last_updated: "<YYYY-MM-DD>"
+---
+
+# <Skill Name>
+
+<One-paragraph skill overview: what it does, who it is for, and why it exists.>
+
+## References
+
+1. [00 <First reference>](references/00-<name>.md)
+
+## Skill layout
+
+- `SKILL.md` — this file (skill entrypoint).
+- `references/` — normative specification documents.
+- `assets/` — reusable constants and format contracts.
+  - `constants/` — constant blocks.
+  - `formats/` — format contracts.
+- `processes/` — executable APS process documents.
+- `guides/` — prose reference documents for humans and agents.
+- `scripts/` — optional build / compile / lint scripts.
diff --git a/.github/skills/agnostic-prompt-standard/_template/assets/constants/.gitkeep b/.github/skills/agnostic-prompt-standard/_template/assets/constants/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/_template/assets/formats/.gitkeep b/.github/skills/agnostic-prompt-standard/_template/assets/formats/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/_template/guides/.gitkeep b/.github/skills/agnostic-prompt-standard/_template/guides/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/_template/processes/.gitkeep b/.github/skills/agnostic-prompt-standard/_template/processes/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/_template/references/.gitkeep b/.github/skills/agnostic-prompt-standard/_template/references/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/_template/scripts/.gitkeep b/.github/skills/agnostic-prompt-standard/_template/scripts/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/assets/composites/gui-component-spec-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/composites/gui-component-spec-v1.0.0.example.md
new file mode 100644
index 0000000..c58a7bc
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/composites/gui-component-spec-v1.0.0.example.md
@@ -0,0 +1,292 @@
+<!-- APS v1.0 — GUI Component Specification (constants + format)
+     This composite asset bundles constants and the format contract for a
+     framework-agnostic GUI component spec with business requirements, design
+     tokens, UX behavior, accessibility, analytics, and child component
+     references. Forward-references child components; never references parent. -->
+
+<constants>
+COMPONENT_SPEC_VERSION: "1.0.0"
+
+SPACING_SCALE: "none | 2xs | xs | sm | md | lg | xl | 2xl | 3xl | 4xl"
+SIZING_MODE: "fixed | fluid | hug | fill | min | max"
+LAYOUT_FLOW: "block | inline | flex_row | flex_col | grid | stack_z | absolute | fixed"
+ALIGN_MAIN: "start | center | end | between | around | evenly"
+ALIGN_CROSS: "start | center | end | stretch | baseline"
+OVERFLOW: "visible | hidden | scroll | auto"
+COLOR_ROLE: "primary | secondary | tertiary | surface | background | error | warning | success | info | on_primary | on_surface | on_background | muted | accent | destructive | border | ring | transparent"
+TYPOGRAPHY_STYLE: "heading_1 | heading_2 | heading_3 | body_lg | body_md | body_sm | caption | overline | code"
+FONT_WEIGHT: "thin | light | normal | medium | semibold | bold | extrabold | black"
+TEXT_ALIGN: "left | center | right | justify"
+TEXT_OVERFLOW: "clip | ellipsis | wrap"
+RADIUS_SCALE: "none | xs | sm | md | lg | xl | full"
+ELEVATION_SCALE: "none | xs | sm | md | lg | xl | 2xl | inner"
+OPACITY_SCALE: "0 | 5 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 95 | 100"
+BORDER_STYLE: "none | solid | dashed | dotted"
+TRANSITION_DURATION: "none | fast | normal | slow"
+TRANSITION_EASING: "linear | ease_in | ease_out | ease_in_out | spring"
+BREAKPOINT: "xs | sm | md | lg | xl | 2xl"
+
+SPACING_EDGE: "all | x | y | top | right | bottom | left | inline | block"
+SIZE_DIMENSION: "width | height"
+LAYOUT_PROPERTY: "display | direction | wrap | align_main | align_cross | overflow | position"
+PRIORITY: "P0_critical | P1_high | P2_medium | P3_low"
+PROP_TYPES: "String | Number | Boolean | Callback | Node | Array | Object | Enum"
+STATE_SCOPES: "local | lifted | global"
+STATE_TYPES: "String | Number | Boolean | Array | Object"
+UX_STATES: "loading | empty | error | success"
+</constants>
+
+<formats>
+<format id="GUI_COMPONENT_SPEC_V1" name="GUI Component Specification" purpose="Define a framework-agnostic GUI component with business requirements, design token mapping, UX behavior, accessibility, analytics, and child component references.">
+# <COMPONENT_NAME>
+
+**Version:** <SPEC_VERSION>
+**Priority:** <PRIORITY>
+**Primary User:** <PRIMARY_USER>
+**Last Updated:** <LAST_UPDATED>
+
+---
+
+## Business Requirements
+
+### User Story
+As a <USER_ROLE>, I want <USER_GOAL> so that <USER_BENEFIT>.
+
+### Acceptance Criteria
+- <ACCEPTANCE_CRITERION>
+…
+
+### Non-functional Requirements
+- <NFR>
+…
+
+### Constraints
+- <CONSTRAINT>
+…
+
+---
+
+## Component Description
+
+<COMPONENT_DESCRIPTION>
+
+---
+
+## Design System Mapping
+
+- Layout Translation: <TOKEN_LAYOUT>
+- Spacing Translation: <TOKEN_SPACING>
+- Aesthetics Translation: <TOKEN_AESTHETICS>
+- Motion Translation: <TOKEN_MOTION>
+
+---
+
+## Layout
+
+| Property | Value | Responsive | Description |
+| --- | --- | --- | --- |
+| <LAYOUT_PROPERTY> | <LAYOUT_VALUE> | <LAYOUT_RESPONSIVE> | <LAYOUT_DESCRIPTION> |
+…
+
+## Spacing
+
+| Edge | Padding | Margin | Gap | Description |
+| --- | --- | --- | --- | --- |
+| <SPACING_EDGE> | <SPACING_PADDING> | <SPACING_MARGIN> | <SPACING_GAP> | <SPACING_DESCRIPTION> |
+…
+
+## Sizing
+
+| Dimension | Mode | Value | Min | Max | Description |
+| --- | --- | --- | --- | --- | --- |
+| <SIZE_DIMENSION> | <SIZE_MODE> | <SIZE_VALUE> | <SIZE_MIN> | <SIZE_MAX> | <SIZE_DESCRIPTION> |
+…
+
+## Typography
+
+| Element | Style | Weight | Align | Overflow | Color | Description |
+| --- | --- | --- | --- | --- | --- | --- |
+| <TYPO_ELEMENT> | <TYPO_STYLE> | <TYPO_WEIGHT> | <TYPO_ALIGN> | <TYPO_OVERFLOW> | <TYPO_COLOR> | <TYPO_DESCRIPTION> |
+…
+
+## Colors and Surfaces
+
+| Target | Role | Value | Opacity | Description |
+| --- | --- | --- | --- | --- |
+| <COLOR_TARGET> | <COLOR_ROLE> | <COLOR_VALUE> | <COLOR_OPACITY> | <COLOR_DESCRIPTION> |
+…
+
+## Borders and Shadows
+
+| Target | Width | Style | Radius | Shadow | Description |
+| --- | --- | --- | --- | --- | --- |
+| <BORDER_TARGET> | <BORDER_WIDTH> | <BORDER_STYLE> | <BORDER_RADIUS> | <BORDER_SHADOW> | <BORDER_DESCRIPTION> |
+…
+
+## Transitions
+
+| Trigger | Property | Duration | Easing | Description |
+| --- | --- | --- | --- | --- |
+| <TRANSITION_TRIGGER> | <TRANSITION_PROPERTY> | <TRANSITION_DURATION> | <TRANSITION_EASING> | <TRANSITION_DESCRIPTION> |
+…
+
+## Responsive Overrides
+
+| Breakpoint | Target | Property | Value | Description |
+| --- | --- | --- | --- | --- |
+| <RESPONSIVE_BREAKPOINT> | <RESPONSIVE_TARGET> | <RESPONSIVE_PROPERTY> | <RESPONSIVE_VALUE> | <RESPONSIVE_DESCRIPTION> |
+…
+
+---
+
+## Props
+
+| Prop | Type | Required | Default | Description |
+| --- | --- | --- | --- | --- |
+| <PROP_NAME> | <PROP_TYPE> | <PROP_REQUIRED> | <PROP_DEFAULT> | <PROP_DESCRIPTION> |
+…
+
+## State
+
+| State Key | Type | Scope | Initial | Description |
+| --- | --- | --- | --- | --- |
+| <STATE_KEY> | <STATE_TYPE> | <STATE_SCOPE> | <STATE_INITIAL> | <STATE_DESCRIPTION> |
+…
+
+## Events
+
+| Event | When | Payload | Description |
+| --- | --- | --- | --- |
+| <EVENT_NAME> | <EVENT_WHEN> | <EVENT_PAYLOAD> | <EVENT_DESCRIPTION> |
+…
+
+---
+
+## UX Behavior
+
+### States
+- **Loading:** <LOADING_BEHAVIOR>
+- **Empty:** <EMPTY_BEHAVIOR>
+- **Error:** <ERROR_BEHAVIOR>
+- **Success:** <SUCCESS_BEHAVIOR>
+
+---
+
+## Accessibility
+
+- <A11Y_NOTE>
+…
+
+---
+
+## Analytics
+
+| Event | Trigger | Payload | Description |
+| --- | --- | --- | --- |
+| <ANALYTICS_EVENT_NAME> | <ANALYTICS_TRIGGER> | <ANALYTICS_PAYLOAD> | <ANALYTICS_DESCRIPTION> |
+…
+
+---
+
+## Child Components
+
+| Child | Purpose |
+| --- | --- |
+| <CHILD_NAME> | <CHILD_PURPOSE> |
+…
+
+---
+
+## Dependencies
+
+- <DEPENDENCY_NAME>: <DEPENDENCY_PURPOSE>
+…
+
+WHERE:
+- <A11Y_NOTE> is String; a component-specific accessibility consideration.
+- <ACCEPTANCE_CRITERION> is String; a single testable condition that must hold; imperative voice.
+- <ANALYTICS_DESCRIPTION> is String; one sentence; what insight this event provides.
+- <ANALYTICS_EVENT_NAME> is String; snake_case tracking event name.
+- <ANALYTICS_PAYLOAD> is String; shape of data sent with the tracking event.
+- <ANALYTICS_TRIGGER> is String; user action or system event that fires the tracking event.
+- <BORDER_RADIUS> is one of: RADIUS_SCALE.
+- <BORDER_SHADOW> is one of: ELEVATION_SCALE.
+- <BORDER_STYLE> is one of: BORDER_STYLE.
+- <BORDER_TARGET> is String; element or edge the border applies to.
+- <BORDER_WIDTH> is one of: SPACING_SCALE; or "none".
+- <CHILD_NAME> is String; name of the child component; forward reference only; parent references are forbidden.
+- <CHILD_PURPOSE> is String; one sentence; what the child component provides to this component.
+- <COLOR_OPACITY> is one of: OPACITY_SCALE; or "100" if fully opaque.
+- <COLOR_ROLE> is one of: COLOR_ROLE.
+- <COLOR_TARGET> is String; element or region the color applies to.
+- <COLOR_VALUE> is String; design system reference or literal value; "—" if role alone suffices.
+- <COMPONENT_DESCRIPTION> is String; 1–3 sentences; what the component renders and its primary responsibility.
+- <COMPONENT_NAME> is String; name of the component.
+- <CONSTRAINT> is String; a business or technical limitation the component must respect.
+- <DEPENDENCY_NAME> is String; package or module name.
+- <DEPENDENCY_PURPOSE> is String; one sentence; why the dependency is needed.
+- <EMPTY_BEHAVIOR> is String; 1–2 sentences; what the component renders when it has no data.
+- <ERROR_BEHAVIOR> is String; 1–2 sentences; what the component renders on failure.
+- <EVENT_DESCRIPTION> is String; one sentence; what the event signals.
+- <EVENT_NAME> is String; callback name.
+- <EVENT_PAYLOAD> is String; shape of data emitted with the event.
+- <EVENT_WHEN> is String; user action or system condition that fires the event.
+- <LAST_UPDATED> is ISO8601.
+- <LAYOUT_DESCRIPTION> is String; one sentence; why this layout choice.
+- <LAYOUT_PROPERTY> is one of: LAYOUT_PROPERTY.
+- <LAYOUT_RESPONSIVE> is Boolean; true if value changes across breakpoints.
+- <LAYOUT_VALUE> is String; semantic token from LAYOUT_FLOW, ALIGN_MAIN, ALIGN_CROSS, or OVERFLOW matching the property.
+- <LOADING_BEHAVIOR> is String; 1–2 sentences; what the component renders while data is pending.
+- <NFR> is String; a non-functional requirement such as performance budget, bundle size limit, or render time target.
+- <PRIMARY_USER> is String; the primary persona or role that interacts with this component.
+- <PRIORITY> is one of: PRIORITY.
+- <PROP_DEFAULT> is String; default value or "—" if none.
+- <PROP_DESCRIPTION> is String; one sentence; what the prop controls.
+- <PROP_NAME> is String; property name.
+- <PROP_REQUIRED> is one of: true, false.
+- <PROP_TYPE> is one of: PROP_TYPES.
+- <RESPONSIVE_BREAKPOINT> is one of: BREAKPOINT.
+- <RESPONSIVE_DESCRIPTION> is String; one sentence; why the override.
+- <RESPONSIVE_PROPERTY> is String; the property being overridden.
+- <RESPONSIVE_TARGET> is String; which section or element the override applies to.
+- <RESPONSIVE_VALUE> is String; the new value at this breakpoint.
+- <SIZE_DESCRIPTION> is String; one sentence; sizing rationale.
+- <SIZE_DIMENSION> is one of: SIZE_DIMENSION.
+- <SIZE_MAX> is String; maximum constraint or "—".
+- <SIZE_MIN> is String; minimum constraint or "—".
+- <SIZE_MODE> is one of: SIZING_MODE.
+- <SIZE_VALUE> is String; token, number with unit, or "—" if mode is hug or fill.
+- <SPACING_DESCRIPTION> is String; one sentence; why this spacing.
+- <SPACING_EDGE> is one of: SPACING_EDGE.
+- <SPACING_GAP> is one of: SPACING_SCALE; or "—".
+- <SPACING_MARGIN> is one of: SPACING_SCALE; or "—".
+- <SPACING_PADDING> is one of: SPACING_SCALE; or "—".
+- <SPEC_VERSION> is String; semantic version of this specification.
+- <STATE_DESCRIPTION> is String; one sentence; what the state tracks.
+- <STATE_INITIAL> is String; initial value expression.
+- <STATE_KEY> is String; state variable name.
+- <STATE_SCOPE> is one of: STATE_SCOPES.
+- <STATE_TYPE> is one of: STATE_TYPES.
+- <SUCCESS_BEHAVIOR> is String; 1–2 sentences; what the component renders on successful data load.
+- <TOKEN_AESTHETICS> is String; summarizes how COLOR_ROLE, TYPOGRAPHY_STYLE, FONT_WEIGHT, RADIUS_SCALE, ELEVATION_SCALE, and OPACITY_SCALE map to the target framework syntax.
+- <TOKEN_LAYOUT> is String; summarizes how LAYOUT_FLOW, ALIGN_MAIN, ALIGN_CROSS, and OVERFLOW map to the target framework syntax.
+- <TOKEN_MOTION> is String; summarizes how TRANSITION_DURATION and TRANSITION_EASING map to the target framework syntax.
+- <TOKEN_SPACING> is String; summarizes how SPACING_SCALE and SIZING_MODE map to the target framework syntax.
+- <TRANSITION_DESCRIPTION> is String; one sentence; transition intent.
+- <TRANSITION_DURATION> is one of: TRANSITION_DURATION.
+- <TRANSITION_EASING> is one of: TRANSITION_EASING.
+- <TRANSITION_PROPERTY> is String; property or semantic target being animated.
+- <TRANSITION_TRIGGER> is String; interaction or state change that starts the transition.
+- <TYPO_ALIGN> is one of: TEXT_ALIGN.
+- <TYPO_COLOR> is one of: COLOR_ROLE.
+- <TYPO_DESCRIPTION> is String; one sentence; typography intent.
+- <TYPO_ELEMENT> is String; element or region the typography applies to.
+- <TYPO_OVERFLOW> is one of: TEXT_OVERFLOW.
+- <TYPO_STYLE> is one of: TYPOGRAPHY_STYLE.
+- <TYPO_WEIGHT> is one of: FONT_WEIGHT.
+- <USER_BENEFIT> is String; the value the user derives from the goal.
+- <USER_GOAL> is String; the action the user wants to perform.
+- <USER_ROLE> is String; the actor or persona using the component.
+- … denotes repetition; one entry per item; each row or bullet follows the same pattern.
+</format>
+</formats>
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/assets/constants/constants-csv-block-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/constants/constants-csv-block-v1.0.0.example.md
new file mode 100644
index 0000000..654db89
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/constants/constants-csv-block-v1.0.0.example.md
@@ -0,0 +1,13 @@
+<!-- Example: multi-line CSV constant using CSV<< ... >>.
+     Engines parse BODY as CSV then compile it to canonical JSON rows (see 00 Structure / 02 Linting). -->
+
+<constants>
+DEFAULT_TZ: "Z"
+
+SERVICE_TABLE: CSV<<
+service,region,default_tz,enabled,note
+billing,us-east-1,DEFAULT_TZ,true,"Primary billing region"
+support,ap-southeast-2,"Australia/Brisbane",true,"Escalations use ""follow the sun"""
+reporting,eu-west-1,DEFAULT_TZ,false,"EU, West"
+>>
+</constants>
diff --git a/.github/skills/agnostic-prompt-standard/assets/constants/constants-json-block-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/constants/constants-json-block-v1.0.0.example.md
new file mode 100644
index 0000000..5f19e58
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/constants/constants-json-block-v1.0.0.example.md
@@ -0,0 +1,15 @@
+<!-- Example: multi-line JSON constant using JSON<< ... >>.
+     Engines parse BODY as JsonValue then compile it to canonical JSON (see json_spacing). -->
+
+<constants>
+DEFAULT_TZ: "Z"
+
+API_CONFIG: JSON<<
+{
+  "api_base_path": "/v1",
+  "default_time_zone": DEFAULT_TZ,
+  "retries": 3,
+  "timeout_ms": 2000
+}
+>>
+</constants>
diff --git a/.github/skills/agnostic-prompt-standard/assets/constants/constants-text-block-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/constants/constants-text-block-v1.0.0.example.md
new file mode 100644
index 0000000..23c288b
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/constants/constants-text-block-v1.0.0.example.md
@@ -0,0 +1,15 @@
+<!-- Example: multi-line TEXT constant using TEXT<< ... >>.
+     NOTE: Comment stripping (//) does NOT apply inside TEXT<< bodies. -->
+
+<constants>
+REPO_TREE: TEXT<<
+cb-agnostic-prompt-protocol
+├── assets
+│   ├── constants
+│   │   └── constants-json-block-v1.0.0.example.md
+│   └── formats
+│       ├── format-code-map-v1.0.0.example.md
+│       └── format-error-v1.0.0.example.md
+└── SKILL.md
+>>
+</constants>
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-code-changes-full-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-code-changes-full-v1.0.0.example.md
new file mode 100644
index 0000000..3e19514
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-code-changes-full-v1.0.0.example.md
@@ -0,0 +1,21 @@
+<format id="CODE_CHANGES_V1" name="Code Changes" purpose="Display updated and new files with complete code.">
+## <CHANGE_TITLE>
+
+<CHANGE_DESCRIPTION>
+File: <FILE_PATH>
+```<LANG>
+<COMPLETE_CODE>
+```
+
+---
+
+…
+
+WHERE:
+- <CHANGE_TITLE> is String; title for the set of changes.
+- <CHANGE_DESCRIPTION> is String; terse description of the change; present voice; NO changelog style.
+- <FILE_PATH> is Path; relative from repository root; MUST NOT start with "/".
+- <LANG> is String; valid code language for GitHub-flavored Markdown.
+- <COMPLETE_CODE> is String; complete file contents; best practices; comments MUST be terse and present voice.
+- … denotes repetition; one block per updated or new file; each separated by "---"; AVOID unchanged files.
+</format>
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-code-map-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-code-map-v1.0.0.example.md
new file mode 100644
index 0000000..7093137
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-code-map-v1.0.0.example.md
@@ -0,0 +1,18 @@
+<format id="CODE_MAP_V1" name="Code Map" purpose="Display relevant code snippets with links to source">
+<AREA_TITLE>
+> [<SHORT_DESC>](../../../<REPO_NAME>/<REL_PATH>#L<LINE_FROM>-L<LINE_TO>)
+```<LANG>
+<LINE_FROM>: <code line>
+<LINE_FROM+1>: <code line>
+…
+<LINE_TO>: <code line>
+```
+
+WHERE:
+- <AREA_TITLE> is the title of the area being described.
+- <REPO_NAME> is a single path segment.
+- <REL_PATH> is repo-relative and MUST NOT start with "/".
+- <LINE_FROM> and <LINE_TO> are integers; LINE_TO ≥ LINE_FROM.
+- <SHORT_DESC> is a short description of the code snippet.
+- <LANG> is a valid code language for GitHub-flavored Markdown.
+</format>
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-docs-index-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-docs-index-v1.0.0.example.md
new file mode 100644
index 0000000..17be2c4
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-docs-index-v1.0.0.example.md
@@ -0,0 +1,25 @@
+<format id="DOCS_INDEX_V1" name="Documentation Index" purpose="Token-efficient hierarchical documentation map for AI navigation.">
+# <PROJECT_TITLE> Documentation Map
+
+> Fetch the complete documentation index at: <INDEX_URL>
+> Last updated: <TIMESTAMP>
+
+## <GROUP_NAME>
+
+### [<PAGE_TITLE>](<PAGE_URL>)
+* <HEADING_TEXT>
+  * <SUBHEADING_TEXT>
+
+...
+
+WHERE:
+- <PROJECT_TITLE> is String; name of the project or documentation set.
+- <INDEX_URL> is URI; URL where this index can be fetched.
+- <TIMESTAMP> is ISO8601; when the index was generated.
+- <GROUP_NAME> is String; documentation section/category name.
+- <PAGE_TITLE> is String; title of the documentation page.
+- <PAGE_URL> is URI; link to the documentation page.
+- <HEADING_TEXT> is String; H2/H3 heading text from the page.
+- <SUBHEADING_TEXT> is String; nested heading under parent.
+- ... denotes repetition; groups contain pages, pages contain headings.
+</format>
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-error-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-error-v1.0.0.example.md
new file mode 100644
index 0000000..8cda4ab
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-error-v1.0.0.example.md
@@ -0,0 +1,9 @@
+<format id="ERROR" name="Format Error" purpose="Emit a single-line reason when a requested format cannot be produced.">
+- Output wrapper starts with a fenced block whose info string is exactly `format:ERROR`.
+- Body is `AG-036 FormatContractViolation: <ONE_LINE_REASON>`.
+- Body MUST be a single line.
+WHERE:
+- <ONE_LINE_REASON> is String.
+- <ONE_LINE_REASON> is ≤ 160 characters.
+- <ONE_LINE_REASON> contains no newlines.
+</format>
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-hierarchical-outline-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-hierarchical-outline-v1.0.0.example.md
new file mode 100644
index 0000000..5bf5084
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-hierarchical-outline-v1.0.0.example.md
@@ -0,0 +1,17 @@
+<format id="OUTLINE_V1" name="Hierarchical Outline" purpose="Generate a semantic multilevel numbered outline.">
+## <OUTLINE_TITLE>
+
+<LEVEL_1_NUMBER> <STATEMENT>
+ <LEVEL_2_NUMBER> <STATEMENT>
+  <LEVEL_3_NUMBER> <STATEMENT>
+
+…
+
+WHERE:
+- <OUTLINE_TITLE> is String; title for the outline.
+- <LEVEL_1_NUMBER> is String; format "N" (e.g., "1", "2", "3").
+- <LEVEL_2_NUMBER> is String; format "N.N" (e.g., "1.1", "1.2").
+- <LEVEL_3_NUMBER> is String; format "N.N.N" (e.g., "1.1.1", "1.1.2"); maximum depth.
+- <STATEMENT> is String; single atomic statement; topic, instruction, or information; NO obvious statements.
+- … denotes repetition; one space indentation per level; up to 3 levels deep.
+</format>
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-ideation-list-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-ideation-list-v1.0.0.example.md
new file mode 100644
index 0000000..ba8df04
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-ideation-list-v1.0.0.example.md
@@ -0,0 +1,20 @@
+<format id="IDEATION_LIST_V1" name="Ideation List" purpose="Generate structured brainstorming ideas for a given task.">
+## <TASK_TITLE>
+
+[<ITEM_NUMBER>] <IDEA_TITLE>
+Summary: <IDEA_SUMMARY>
+Details: <IDEA_DETAILS>
+
+---
+
+…
+
+WHERE:
+- <TASK_TITLE> is String; the task or topic for ideation.
+- <ITEM_COUNT> is Integer; total number of ideation items to generate.
+- <ITEM_NUMBER> is Integer; sequential from 1 to <ITEM_COUNT>.
+- <IDEA_TITLE> is String; short descriptive title; present tense; active voice.
+- <IDEA_SUMMARY> is String; one sentence; present tense; active voice.
+- <IDEA_DETAILS> is String; 2–4 sentences; conceptual only; NO implementation, code, or pseudo-code.
+- … denotes repetition; exactly <ITEM_COUNT> items; each separated by "---".
+</format>
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-link-manifest-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-link-manifest-v1.0.0.example.md
new file mode 100644
index 0000000..d12dc64
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-link-manifest-v1.0.0.example.md
@@ -0,0 +1,13 @@
+<format id="LINK_MANIFEST_V1" name="Link Manifest" purpose="Flat documentation listing with links and descriptions for quick AI navigation.">
+# <MANIFEST_TITLE>
+
+- [<LINK_TITLE>](<LINK_URL>): <LINK_DESCRIPTION>
+...
+
+WHERE:
+- <MANIFEST_TITLE> is String; title of the manifest or documentation set.
+- <LINK_TITLE> is String; display title for the link.
+- <LINK_URL> is URI; URL to the resource.
+- <LINK_DESCRIPTION> is String; brief description of the linked resource (one sentence).
+- ... denotes repetition; each link entry follows the same pattern.
+</format>
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-markdown-table-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-markdown-table-v1.0.0.example.md
new file mode 100644
index 0000000..f2b9489
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-markdown-table-v1.0.0.example.md
@@ -0,0 +1,17 @@
+<format id="TABLE_PROCESS_RESULTS_V1" name="Process Results Table" purpose="Summarize process execution across processes in lexical order.">
+- Output wrapper starts with a fenced block whose info string is exactly `format:TABLE_PROCESS_RESULTS_V1`.
+- Header row MUST be:
+  | ProcessId | Name | Status | StartedAt | EndedAt | DurationMs | Outcome | Artifacts | Errors |
+- Example row:
+  | <PROCESS_ID> | <PROCESS_NAME> | <STATUS> | <STARTED_AT> | <ENDED_AT> | <DURATION_MS> | <OUTCOME> | <ARTIFACTS> | <ERRORS> |
+WHERE:
+- <PROCESS_ID> is String.
+- <PROCESS_NAME> is String.
+- <STATUS> is one of: PENDING, RUNNING, OK, WARN, ERROR.
+- <STARTED_AT> is ISO8601.
+- <ENDED_AT> is ISO8601.
+- <DURATION_MS> is Integer.
+- <OUTCOME> is String.
+- <ARTIFACTS> is String.
+- <ERRORS> is String.
+</format>
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-smeac-plan-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-smeac-plan-v1.0.0.example.md
new file mode 100644
index 0000000..7a9a6ed
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-smeac-plan-v1.0.0.example.md
@@ -0,0 +1,186 @@
+```markdown
+<format id="SMEAC_PLAN_V1" name="SMEAC Plan" purpose="Structured planning brief covering situation, mission, execution phases, logistics, and command.">
+# <PLAN_TITLE>
+
+**Prepared:** <TIMESTAMP>
+**Classification:** <CLASSIFICATION>
+
+---
+
+## 1. Situation
+
+### Operating Environment
+<OPERATING_ENVIRONMENT>
+
+### Current State
+<CURRENT_STATE>
+
+### Challenges & Obstacles
+- <OBSTACLE>: <OBSTACLE_ASSESSMENT>
+…
+
+### Supporting Factors
+- **Higher intent:** <HIGHER_INTENT>
+- **Adjacent efforts:** <ADJACENT_EFFORTS>
+- **Supporting resources:** <SUPPORTING_RESOURCES>
+
+### Assumptions
+- <ASSUMPTION>
+…
+
+### Constraints & Limitations
+- **Constraint:** <CONSTRAINT>
+- **Limitation:** <LIMITATION>
+…
+
+---
+
+## 2. Mission
+
+<MISSION_STATEMENT>
+
+### Task
+<TASK>
+
+### Purpose
+<PURPOSE>
+
+### End State
+<END_STATE>
+
+---
+
+## 3. Execution
+
+### Leader's Intent
+<LEADERS_INTENT>
+
+### Concept of Operations
+<CONCEPT_OF_OPERATIONS>
+
+### Phases
+
+#### Phase <PHASE_NUMBER>: <PHASE_NAME>
+- **Objective:** <PHASE_OBJECTIVE>
+- **Key tasks:**
+  - <PHASE_TASK>
+  …
+- **Success criteria:** <PHASE_SUCCESS_CRITERIA>
+- **Transition trigger:** <TRANSITION_TRIGGER>
+…
+
+### Coordinating Instructions
+- **Timeline:** <TIMELINE>
+- **Boundaries:** <BOUNDARIES>
+- **Operating guidelines:** <OPERATING_GUIDELINES>
+- **Risk mitigation:** <RISK_MITIGATION>
+
+### Contingencies
+- **If** <CONTINGENCY_CONDITION> **then** <CONTINGENCY_ACTION>
+…
+
+---
+
+## 4. Admin & Logistics
+
+### Resources Required
+| Resource | Quantity | Source | Status |
+| --- | --- | --- | --- |
+| <RESOURCE_NAME> | <RESOURCE_QUANTITY> | <RESOURCE_SOURCE> | <RESOURCE_STATUS> |
+…
+
+### Supply & Provisioning
+<SUPPLY_PLAN>
+
+### Transportation & Movement
+<TRANSPORTATION_PLAN>
+
+### Sustainment
+<SUSTAINMENT_PLAN>
+
+### Recovery / Rollback Plan
+<ROLLBACK_PLAN>
+
+---
+
+## 5. Command & Signal
+
+### Decision Chain
+1. <PRIMARY_LEAD>
+2. <SUCCESSOR_LEAD>
+…
+
+### Communications Plan
+| Channel | Medium | Purpose | Cadence |
+| --- | --- | --- | --- |
+| <CHANNEL_NAME> | <CHANNEL_MEDIUM> | <CHANNEL_PURPOSE> | <CHANNEL_CADENCE> |
+…
+
+### Reporting Requirements
+- <REPORTING_REQUIREMENT>
+…
+
+### Decision Authority
+| Decision | Authority | Escalation |
+| --- | --- | --- |
+| <DECISION_TYPE> | <DECISION_AUTHORITY> | <ESCALATION_PATH> |
+…
+
+### Acknowledgement
+All parties MUST acknowledge receipt and understanding of this plan.
+
+---
+
+WHERE:
+- <PLAN_TITLE> is String; concise name for the plan or operation.
+- <TIMESTAMP> is ISO8601; date/time the plan was prepared.
+- <CLASSIFICATION> is one of: PUBLIC, INTERNAL, CONFIDENTIAL, RESTRICTED.
+- <OPERATING_ENVIRONMENT> is String; 1–3 sentences; describes the domain, environment, or scope of operations.
+- <CURRENT_STATE> is String; 1–3 sentences; factual assessment of the current situation and relevant background.
+- <OBSTACLE> is String; name or category of a challenge, competitor, blocker, or risk.
+- <OBSTACLE_ASSESSMENT> is String; impact, likelihood, and probable course of action for the obstacle.
+- <HIGHER_INTENT> is String; the overarching goal from leadership or strategy that this plan supports.
+- <ADJACENT_EFFORTS> is String; related parallel initiatives, teams, or workstreams and their relevance.
+- <SUPPORTING_RESOURCES> is String; available assets, teams, tools, or capabilities that can be leveraged.
+- <ASSUMPTION> is String; a condition assumed to be true for planning purposes; must be validated before or during execution.
+- <CONSTRAINT> is String; a restriction imposed by leadership or policy that limits freedom of action (MUST do or MUST NOT do).
+- <LIMITATION> is String; a shortcoming in capability or resource that restricts options.
+- <MISSION_STATEMENT> is String; single sentence; answers who, what, when, where, and why; active voice; present tense.
+- <TASK> is String; the specific action to be accomplished; measurable and time-bound.
+- <PURPOSE> is String; the reason the task matters; links to higher intent.
+- <END_STATE> is String; describes the desired conditions when the mission is complete.
+- <LEADERS_INTENT> is String; 2–4 sentences; states the purpose, key tasks, and desired end state in the leader's own framing.
+- <CONCEPT_OF_OPERATIONS> is String; 2–5 sentences; high-level approach describing how phases combine to achieve the mission.
+- <PHASE_NUMBER> is Integer; sequential from 1.
+- <PHASE_NAME> is String; short descriptive name for the phase (e.g., "Preparation", "Execution", "Consolidation").
+- <PHASE_OBJECTIVE> is String; what this phase aims to achieve.
+- <PHASE_TASK> is String; a discrete task within the phase; actionable and assignable.
+- <PHASE_SUCCESS_CRITERIA> is String; measurable conditions that indicate the phase objective is met.
+- <TRANSITION_TRIGGER> is String; the event or condition that signals transition to the next phase; last phase uses "Mission complete" or equivalent.
+- <TIMELINE> is String; key dates, deadlines, or time windows for execution.
+- <BOUNDARIES> is String; scope limits, geographic or logical boundaries, and deconfliction lines.
+- <OPERATING_GUIDELINES> is String; guidelines governing actions, decisions, and interactions during execution.
+- <RISK_MITIGATION> is String; identified risks and their mitigations.
+- <CONTINGENCY_CONDITION> is String; a specific adverse event or deviation from plan.
+- <CONTINGENCY_ACTION> is String; the prescribed response to the contingency condition.
+- <RESOURCE_NAME> is String; name or type of resource (personnel, equipment, budget, tooling, etc.).
+- <RESOURCE_QUANTITY> is String; amount or count required.
+- <RESOURCE_SOURCE> is String; where the resource comes from (team, vendor, budget line, etc.).
+- <RESOURCE_STATUS> is one of: AVAILABLE, REQUESTED, PENDING, AT_RISK, UNAVAILABLE.
+- <SUPPLY_PLAN> is String; 1–3 sentences; how consumable resources will be sourced and distributed.
+- <TRANSPORTATION_PLAN> is String; 1–3 sentences; how assets, deliverables, or personnel move between locations or stages.
+- <SUSTAINMENT_PLAN> is String; 1–3 sentences; how the operation will be maintained over its duration.
+- <ROLLBACK_PLAN> is String; 1–3 sentences; procedure for reverting or recovering if execution fails.
+- <PRIMARY_LEAD> is String; name and role of the primary decision-maker.
+- <SUCCESSOR_LEAD> is String; name and role of the next in line; at least one successor required.
+- <CHANNEL_NAME> is String; identifier for the communication channel (e.g., "Primary", "Backup", "Emergency").
+- <CHANNEL_MEDIUM> is String; the medium of communication (e.g., "Slack", "Email", "Teams", "In-person").
+- <CHANNEL_PURPOSE> is String; what this channel is used for (e.g., "Coordination", "Status updates", "Escalation").
+- <CHANNEL_CADENCE> is String; frequency of communication (e.g., "Real-time", "Daily standup", "On event").
+- <REPORTING_REQUIREMENT> is String; a specific report, metric, or status update expected during or after execution.
+- <DECISION_TYPE> is String; category of decision (e.g., "Go/No-go", "Resource allocation", "Scope change").
+- <DECISION_AUTHORITY> is String; who has authority to make this decision.
+- <ESCALATION_PATH> is String; who to escalate to if the primary authority is unavailable.
+- … denotes repetition; items follow the same pattern for each entry in the section.
+</format>
+```
diff --git a/.github/skills/agnostic-prompt-standard/assets/formats/format-table-api-coverage-v1.0.0.example.md b/.github/skills/agnostic-prompt-standard/assets/formats/format-table-api-coverage-v1.0.0.example.md
new file mode 100644
index 0000000..ef24c28
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/assets/formats/format-table-api-coverage-v1.0.0.example.md
@@ -0,0 +1,13 @@
+<format id="TABLE_API_COVERAGE_V1" name="API Coverage Table" purpose="Report API operation coverage against a specification.">
+## <TABLE_NAME>
+| Operation | URI | SpecRef | Gap |
+| --- | --- | --- | --- |
+| <OPERATION> | <URI> | <SPEC_REF> | <GAP> |
+
+WHERE:
+- <TABLE_NAME> is the title for the API coverage table.
+- <OPERATION> is the HTTP method, one of: `GET`, `POST`, `PUT`, `PATCH`, `DELETE`, `HEAD`, `OPTIONS`.
+- <URI> is the absolute path of the API endpoint, starting with `/`.
+- <SPEC_REF> is a reference to the relevant part of the API specification, one of: `OpenAPI: <PATH_OR_COMPONENT>` or `Swagger: <PATH_OR_COMPONENT>`.
+- <GAP> is the coverage gap analysis code, one of: `OK`, `MISSING_PATH`, `MISSING_METHOD`, `REQ_SCHEMA_MISMATCH`, `RESP_SCHEMA_MISMATCH`, `STATUS_CODE_MISSING`.
+</format>
diff --git a/.github/skills/agnostic-prompt-standard/guides/skill-authoring-v1.0.0.guide.md b/.github/skills/agnostic-prompt-standard/guides/skill-authoring-v1.0.0.guide.md
new file mode 100644
index 0000000..01d32d2
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/guides/skill-authoring-v1.0.0.guide.md
@@ -0,0 +1,193 @@
+<instructions>
+You MUST create a SKILL.md file as the entrypoint for every skill.
+You MUST use kebab-case for the skill directory name.
+You MUST start SKILL.md with YAML frontmatter between --- delimiters.
+You SHOULD include name and description fields in frontmatter.
+You SHOULD include a metadata sub-object with author and spec_version.
+You MUST structure the SKILL.md body as: title, overview, references, skill layout.
+You MUST name reference files using the NN-<name>.md convention.
+You MUST write references as prose markdown, not APS envelopes.
+You MUST use normative language (MUST, SHOULD, MAY) in reference documents.
+You MUST use active voice and imperative mood in reference procedures.
+You SHOULD organize references with one topic per section using H2/H3 headings.
+You MUST use relative markdown paths for cross-references within a skill.
+You MUST name constant asset files as constants-<descriptor>-v<VERSION>.example.md.
+You MUST name format asset files as format-<descriptor>-v<VERSION>.example.md.
+You MUST name composite asset files as <descriptor>-v<VERSION>.example.md.
+You MUST use UPPER_SNAKE_CASE matching ^[A-Z0-9_]{2,24}$ for constant symbols.
+You MUST place exactly one ASCII space after the colon in block constant openers.
+You MUST place the closing >> at column 1 on its own line.
+You MUST give every format a unique id in UPPER_SNAKE_CASE with version suffix.
+You MUST define a WHERE entry for every <PLACEHOLDER> in a format body.
+You MUST use <UPPER_SNAKE> notation for all format placeholders.
+You MUST structure process files as APS documents following section ordering.
+You SHOULD omit APS sections that carry no content.
+You MUST name process files as <process-name>.md in kebab-case.
+You MUST backtick all process and tool IDs in DSL statements.
+You MUST order where: keys in lexicographic order.
+You MUST use logical tool names that platform adapters resolve.
+You MUST NOT use tab characters in any skill file.
+You MUST NOT use comment syntax inside APS sections.
+You MUST NOT use smart quotes; use ASCII double quotes only.
+You MAY add a license field using an SPDX identifier in frontmatter.
+You MAY add a version field for standalone skill versioning in frontmatter.
+</instructions>
+
+<constants>
+GUIDE_VERSION: "1.0.0"
+
+SKILLMD_BODY_SECTIONS: TEXT<<
+1. Title — # <Skill Name> as an H1 heading.
+2. Overview — One paragraph covering what the skill does, who uses it, and why.
+3. References — Numbered list linking to each document in references/.
+4. Skill layout — Bullet-list tree of directory contents with one-line descriptions.
+>>
+
+FRONTMATTER_FIELDS: CSV<<
+field,required,notes
+name,Recommended,"Skill identifier, kebab-case"
+description,Recommended,"Single sentence, double-quoted"
+license,Optional,"SPDX identifier (e.g. MIT, Apache-2.0)"
+version,Optional,SemVer string for standalone versioning
+metadata,Recommended,Structured sub-object for provenance
+>>
+
+METADATA_SUBFIELDS: TEXT<<
+repository — URL of the source repository.
+author — Primary author name.
+co_authors — Semicolon-delimited list of co-author names.
+spec_version — APS spec version targeted (e.g. 1.0).
+framework_revision — Skill version in SemVer format.
+last_updated — ISO 8601 date of last modification.
+>>
+
+REFERENCE_CONTENT_RULES: TEXT<<
+Use normative language from 01-vocabulary.md: MUST, MUST NOT, SHOULD, SHOULD NOT, MAY.
+Use active voice and imperative or declarative mood.
+Limit one topic per section with clear H2/H3 headings.
+Use tables for structured rules and lists for enumerations.
+Use fenced code blocks with language identifiers for examples.
+Link between documents using relative markdown paths.
+All links must resolve to files within the skill directory.
+Fragment anchors (#heading) are allowed for linking to specific sections.
+>>
+
+BLOCK_TYPE_REF: CSV<<
+block_type,use_case,key_rules
+JSON,Structured data,"Lexicographic key order, canonical spacing"
+TEXT,Literal text,Preserved verbatim after newline normalization
+YAML,Configuration,"2-space indent, lexicographic key order"
+CSV,Tabular data,"Header row + records, same field count per row"
+>>
+
+BLOCK_SYNTAX_RULES: TEXT<<
+Opener: SYMBOL: TYPE<< with exactly one ASCII space after the colon and no spaces before <<.
+Closer: >> on its own line at column 1 with no leading or trailing whitespace.
+Body: content between the newline after the opener and the newline before the closer.
+>>
+
+FORMAT_WHERE_TYPES: TEXT<<
+String — Free-text value.
+Integer — Whole number value.
+Number — Numeric value (integer or decimal).
+Boolean — true or false.
+ISO8601 — ISO 8601 date or datetime string.
+Markdown — Markdown-formatted text (lists, headings, inline formatting).
+URI — Uniform resource identifier.
+Path — File or directory path.
+>>
+
+COMPOSITE_ASSET_DESC: TEXT<<
+Composites bundle tightly coupled constants and formats in a single file.
+The format references the constants as its type vocabulary.
+File naming: <descriptor>-v<VERSION>.example.md in assets/composites/.
+>>
+
+DSL_KEYWORD_REF: TEXT<<
+RUN — Invoke a sub-process. Example: RUN `sub-process`.
+USE — Invoke a tool with parameters. Example: USE `Read` where: path="file.md".
+CAPTURE — Bind a tool result to a variable. Example: CAPTURE RESULT from `Read`.
+SET — Assign a value to a variable. Example: SET VAR := "value" (from "Agent Inference").
+IF / ELSE — Conditional branching. Example: IF condition:.
+PAR / JOIN — Execute statements concurrently. Example: PAR: ... JOIN:.
+FOREACH — Iterate over a collection. Example: FOREACH ITEM IN COLLECTION:.
+TELL — Emit narrative output to the user. Example: TELL "message" level=brief.
+RETURN — Exit a process with a formatted result. Example: RETURN: format="ID", key=value.
+TRY / RECOVER — Handle errors in process execution. Example: TRY: ... RECOVER ERR:.
+>>
+
+DSL_CRITICAL_RULES: TEXT<<
+Process and tool IDs must be backticked: `process-id`, `Read`.
+where: keys must be in lexicographic order (AG-012).
+Use logical tool names (Read, Write, Glob) that platform adapters resolve.
+No tabs (AG-011), no comments (AG-010), no smart quotes.
+>>
+
+DESIGN_PATTERNS: JSON<<
+{
+  "compliance-checker": {
+    "description": "Validates artifacts against a set of rules",
+    "emphasis": "references + processes + formats",
+    "example_dirs": ["assets/formats/", "processes/", "references/"]
+  },
+  "domain-vocabulary": {
+    "description": "Defines a shared language for a specific domain",
+    "emphasis": "references + constants",
+    "example_dirs": ["assets/constants/", "assets/formats/", "references/"]
+  },
+  "library-wrapper": {
+    "description": "Wraps an external library, SDK, or API as a skill",
+    "emphasis": "references + constants + processes",
+    "example_dirs": ["assets/constants/", "assets/formats/", "processes/", "references/"]
+  },
+  "workflow": {
+    "description": "Encodes a multi-step business or engineering workflow",
+    "emphasis": "references + processes",
+    "example_dirs": ["processes/", "references/"]
+  }
+}
+>>
+
+COMMON_PITFALLS: TEXT<<
+Missing WHERE clauses — Format placeholders without type definitions trigger AG-041. Fix: add a WHERE entry for every placeholder in the format body.
+Tab characters — Tabs in any APS section trigger AG-011. Fix: use spaces only; configure editor to insert spaces.
+Smart quotes — Curly quotes break string parsing. Fix: use straight ASCII double quotes only.
+Unbackticked IDs — Process and tool IDs without backticks trigger AG-003. Fix: always wrap IDs in backticks.
+Orphan constants — Constants defined but never referenced. Fix: remove unused constants or reference them in processes or formats.
+Platform-specific tool names — Hardcoded tool names break portability. Fix: use logical names (Read, Write, Glob) and let the adapter resolve them.
+Blank lines in instructions — Empty lines inside instructions trigger AG-033. Fix: remove all blank lines; every line must contain a directive.
+Multi-sentence lines — Multiple sentences on one line in instructions trigger AG-033. Fix: one directive per line, max 20 words.
+>>
+</constants>
+
+<formats>
+<format id="SKILL_ANATOMY_V1" name="Skill Anatomy" purpose="Summarize a skill directory structure and composition for review">
+## Skill Anatomy: <SKILL_ID>
+
+**Pattern:** <PATTERN_NAME>
+
+### Directory tree
+<DIR_TREE>
+
+### Composition
+| Component | Count |
+|-----------|-------|
+| References | <REF_COUNT> |
+| Constants | <CONST_COUNT> |
+| Formats | <FMT_COUNT> |
+| Processes | <PROC_COUNT> |
+
+### Design notes
+<DESIGN_NOTES>
+
+WHERE:
+- <CONST_COUNT> is Integer; number of constant asset files.
+- <DESIGN_NOTES> is Markdown; architectural observations and recommendations.
+- <DIR_TREE> is String; ASCII tree showing the skill directory layout.
+- <FMT_COUNT> is Integer; number of format asset files.
+- <PATTERN_NAME> is String; one of library-wrapper, workflow, domain-vocabulary, compliance-checker.
+- <PROC_COUNT> is Integer; number of process files.
+- <REF_COUNT> is Integer; number of reference documents.
+- <SKILL_ID> is String; kebab-case skill directory name.
+</format>
+</formats>
diff --git a/.github/skills/agnostic-prompt-standard/platforms/README.md b/.github/skills/agnostic-prompt-standard/platforms/README.md
new file mode 100644
index 0000000..ea6173a
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/README.md
@@ -0,0 +1,52 @@
+# Platforms
+
+APS is designed to be **platform-agnostic**, but real hosts (IDEs, agent runtimes, CI bots) differ in:
+
+- File discovery conventions (where prompts/agents/skills live)
+- YAML frontmatter dialects (which fields exist, required/optional)
+- Tool availability, naming, and approval UX
+- Safety constraints (auto-approve settings, restricted file paths)
+
+This folder contains **platform adapters** that describe those differences *without changing the APS v1.0 spec*.
+
+## Adapter layout
+
+Each platform adapter is a single `adaptor.md` file plus an optional `templates/` directory:
+
+```
+platforms/
+  _template/                      # skeleton for new adapters
+    adaptor.md                    # template adaptor.md
+    templates/                    # optional installable agent files
+  <platform-id>/
+    adaptor.md                    # single source of truth
+    templates/                    # optional installable agent files
+      .claude/agents/             # (claude-code) or
+      .github/agents/             # (vscode-copilot)
+```
+
+The `adaptor.md` file contains three APS sections:
+
+1. `<instructions>` — platform-specific generation instructions
+2. `<constants>` — all metadata: platform ID, detection markers, file conventions, tool registries, agent versioning
+3. `<formats>` — frontmatter and output format contracts
+
+## Add a new platform adapter
+
+1. Copy `platforms/_template/` to `platforms/<platform-id>/`
+2. Fill in `adaptor.md` with platform-specific constants and formats
+3. Optionally add a `templates/` directory with installable agent files
+4. Do **not** change `references/` unless you are intentionally publishing an APS spec revision
+
+## Contract
+
+- Anything under `references/` is **normative** APS.
+- Anything under `platforms/` is **non-normative** (documentation/templates/mappings only).
+- Adapters should prefer **mapping + configuration** over rewriting APS core rules.
+
+## Scope and Philosophy
+
+Adapters are intended to **map** the APS standard to a host platform. They are **not** project generators.
+We do not provide generic project scaffolding (like `settings.json` or root `CLAUDE.md` templates).
+
+> See [ADR 0001: Adapter Scope](https://github.com/chris-buckley/agnostic-prompt-standard/blob/main/docs/adr/0001-adapter-scope-no-scaffolding.md)
diff --git a/.github/skills/agnostic-prompt-standard/platforms/_template/adaptor.md b/.github/skills/agnostic-prompt-standard/platforms/_template/adaptor.md
new file mode 100644
index 0000000..9e79355
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/_template/adaptor.md
@@ -0,0 +1,20 @@
+<instructions>
+Replace this section with platform-specific generation instructions.
+Describe tool naming conventions, file locations, and frontmatter rules.
+</instructions>
+
+<constants>
+PLATFORM_ID: "your-platform-id"
+DISPLAY_NAME: "Your Platform"
+ADAPTER_VERSION: "0.1.0"
+LAST_UPDATED: "YYYY-MM-DD"
+
+INSTRUCTION_FILE_PATHS: [".github/copilot-instructions.md"]
+
+DETECTION_MARKERS: [".github/agents/", "path/to/marker.file"]
+
+DOCS_HOME_URL: "https://example.com/docs"
+</constants>
+
+<formats>
+</formats>
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/platforms/_template/templates/.github/agents/.gitkeep b/.github/skills/agnostic-prompt-standard/platforms/_template/templates/.github/agents/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/.github/skills/agnostic-prompt-standard/platforms/claude-code/adaptor.md b/.github/skills/agnostic-prompt-standard/platforms/claude-code/adaptor.md
new file mode 100644
index 0000000..b6b2343
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/claude-code/adaptor.md
@@ -0,0 +1,177 @@
+<instructions>
+Generate artifacts for Claude Code CLI using the constants and format contracts in this adapter.
+Tool names are PascalCase and used directly without qualification or prefixes.
+MCP tools use the pattern: mcp__<server>__<tool>.
+Subagents are stored in .claude/agents/*.md with YAML frontmatter.
+Rules are stored in .claude/rules/*.md with optional path-scoped YAML frontmatter.
+File imports use @path syntax (e.g., @README.md, @docs/guide.md, @~/.claude/shared-rules.md).
+Hooks execute shell commands at lifecycle events and are configured in .claude/settings.json.
+Permissions use Tool(specifier) with allow/deny/ask arrays in .claude/settings.json.
+Tools in frontmatter are comma-separated strings (e.g., tools: Read, Write, Edit).
+</instructions>
+
+<constants>
+PLATFORM_ID: "claude-code"
+DISPLAY_NAME: "Claude Code CLI"
+ADAPTER_VERSION: "2.0.0"
+LAST_UPDATED: "2026-02-19"
+
+INSTRUCTION_FILE_PATHS: ["./CLAUDE.md", "./.claude/CLAUDE.md", "./.claude/rules/*.md", "./CLAUDE.local.md", "~/.claude/CLAUDE.md", "~/.claude/rules/*.md"]
+AGENT_FILE_PATHS: ["./.claude/agents/*.md", "~/.claude/agents/*.md"]
+MCP_CONFIG_PATHS: ["./.mcp.json"]
+SETTINGS_FILE_PATHS: ["./.claude/settings.json", "./.claude/settings.local.json", "~/.claude/settings.json"]
+MEMORY_LOAD_ORDER: [INSTRUCTION_FILE_PATHS, AGENT_FILE_PATHS, MCP_CONFIG_PATHS, SETTINGS_FILE_PATHS]
+
+DETECTION_MARKERS: [".claude", "CLAUDE.md", "CLAUDE.local.md", ".mcp.json", ".claude/settings.json", ".claude/agents", ".claude/rules"]
+
+MEMORY_LEVEL_ENTERPRISE: "Managed by organization admins."
+MEMORY_LEVEL_PROJECT: ["./CLAUDE.md", "./.claude/CLAUDE.md"]
+MEMORY_LEVEL_RULES: ["./.claude/rules/*.md"]
+MEMORY_LEVEL_USER: ["~/.claude/CLAUDE.md", "./CLAUDE.local.md"]
+MEMORY_OVERRIDE_ORDER: [MEMORY_LEVEL_ENTERPRISE, MEMORY_LEVEL_PROJECT, MEMORY_LEVEL_RULES, MEMORY_LEVEL_USER]
+
+HOOK_EVENTS: ["PreToolUse", "PostToolUse", "PermissionRequest", "Stop", "SubagentStop", "UserPromptSubmit", "SessionStart", "SessionEnd", "PreCompact", "Notification"]
+HOOK_CONFIG_PATH: ".claude/settings.json"
+
+TOOL_NAMING_STYLE: "PascalCase"
+TOOL_NAMING_QUALIFICATION: "none"
+MCP_TOOL_PATTERN: "mcp__<server>__<tool>"
+TOOL_FRONTMATTER_SYNTAX: "comma-separated strings (e.g., tools: Read, Write, Edit, Bash)"
+
+TOOLS: CSV<<
+name,toolset,risk,side_effects,description,params
+Read,filesystem,low,reads,"Read file contents. Supports text/images/PDFs/notebooks.","[file_path:string:required, offset:integer:optional, limit:integer:optional, pages:string:optional]"
+Write,filesystem,medium,writes,"Create or overwrite files. Read first if exists. Prefer Edit.","[file_path:string:required, content:string:required]"
+Edit,filesystem,medium,writes,"Exact string replacement. old_string must be unique.","[file_path:string:required, old_string:string:required, new_string:string:required, replace_all:boolean:optional]"
+Glob,filesystem,low,reads,"Find files by glob pattern. Returns paths sorted by modification time.","[pattern:string:required, path:string:optional]"
+Grep,filesystem,low,reads,"Search file contents using regex (ripgrep). Use glob/type for filtering.","[pattern:string:required, path:string:optional, glob:string:optional, type:string:optional, output_mode:enum(content|files_with_matches|count):optional]"
+NotebookEdit,filesystem,medium,writes,"Replace/insert/delete cells in Jupyter notebooks.","[notebook_path:string:required, new_source:string:required, cell_id:string:optional, cell_type:enum(code|markdown):optional, edit_mode:enum(replace|insert|delete):optional]"
+Bash,execution,high,executes,"Execute bash commands. Use for git/npm/docker. Avoid for file ops.","[command:string:required, description:string:optional, timeout:integer:optional, run_in_background:boolean:optional]"
+Task,execution,medium,mixed,"Launch specialized subagents for complex multi-step tasks.","[description:string:required, prompt:string:required, subagent_type:string:required, model:enum(sonnet|opus|haiku):optional, run_in_background:boolean:optional, max_turns:integer:optional]"
+TaskOutput,execution,low,reads,"Retrieve output from running or completed background task.","[task_id:string:required, block:boolean:optional, timeout:integer:optional]"
+TaskStop,execution,low,executes,"Stop a running background task by ID.","[task_id:string:required]"
+TaskCreate,execution,low,none,"Create a new task in the structured task list.","[subject:string:required, description:string:required, activeForm:string:optional]"
+TaskUpdate,execution,low,none,"Update task status/details/dependencies.","[taskId:string:required, status:enum(pending|in_progress|completed|deleted):optional, subject:string:optional, description:string:optional]"
+TaskList,execution,low,reads,"List all tasks with status and dependencies.",""
+TaskGet,execution,low,reads,"Get full details of a specific task by ID.","[taskId:string:required]"
+TodoWrite,execution,low,none,"Create and manage structured task/todo items for tracking session progress.","[subject:string:required, description:string:required, activeForm:string:optional]"
+MCPSearch,execution,low,reads,"Search for and load MCP tools. Requires MCP servers configured.",""
+WebFetch,web,medium,network,"Fetch URL content and process with prompt. 15-min cache. Fails for auth URLs.","[url:string:required, prompt:string:required]"
+WebSearch,web,medium,network,"Search the web. Must include Sources section with URLs.","[query:string:required, allowed_domains:array:optional, blocked_domains:array:optional]"
+AskUserQuestion,interaction,low,none,"Ask user questions. 1-4 questions with 2-4 options each.","[questions:array:required]"
+Skill,skills,medium,mixed,"Execute a skill (slash command) within the conversation.","[skill:string:required, args:string:optional]"
+EnterPlanMode,planning,low,none,"Transition to plan mode for implementation approaches.",""
+ExitPlanMode,planning,low,none,"Signal plan completion and request user approval.","[allowedPrompts:array:optional, pushToRemote:boolean:optional]"
+LSP,code_intelligence,low,reads,"Code intelligence via Language Server Protocol. IDE-only.",""
+>>
+
+RECOMMENDED_PLANNER_TOOLS: ["Read", "Glob", "Grep", "WebFetch", "WebSearch", "TaskCreate", "TaskUpdate", "TaskList", "TaskGet", "AskUserQuestion", "Task"]
+RECOMMENDED_IMPLEMENTER_TOOLS: ["Read", "Write", "Edit", "Bash", "Glob", "Grep", "TaskCreate", "TaskUpdate", "TaskList", "TaskGet", "Task", "NotebookEdit"]
+
+PERMISSION_MODES: ["default", "acceptEdits", "dontAsk", "bypassPermissions", "plan"]
+AGENT_MODELS: ["sonnet", "opus", "haiku", "inherit"]
+
+AGENT_VERSIONING: JSON<<
+{
+  "templates": [
+    {
+      "path": "templates/.claude/agents/aps-v{major}.{minor}.{patch}.md",
+      "current_path": "templates/.claude/agents/aps-v1.1.16.md",
+      "frontmatter": {
+        "name_pattern": "aps-v{major}-{minor}-{patch}",
+        "description_pattern": "Generate APS v{major}.{minor}.{patch} agent files for any platform: load APS skill + target platform adapter, extract intent, then generate+write+lint."
+      }
+    }
+  ]
+}
+>>
+
+SKILL_AUTHORING_RESOURCES: JSON<<
+{
+  "guide": "guides/skill-authoring-v1.0.0.guide.md",
+  "template": "_template/",
+  "build_process": "processes/build-skill.md"
+}
+>>
+
+DOCS_MEMORY_URL: "https://docs.anthropic.com/en/docs/claude-code/memory"
+DOCS_SETTINGS_URL: "https://docs.anthropic.com/en/docs/claude-code/settings"
+DOCS_HOOKS_URL: "https://docs.anthropic.com/en/docs/claude-code/hooks"
+DOCS_MCP_URL: "https://docs.anthropic.com/en/docs/claude-code/mcp"
+DOCS_TOOLS_URL: "https://docs.anthropic.com/en/docs/claude-code/cli-reference"
+DOCS_SUBAGENTS_URL: "https://docs.anthropic.com/en/docs/claude-code/sub-agents"
+</constants>
+
+<formats>
+<format id="CC_AGENT_FRONTMATTER_V1" name="Claude Code Agent Frontmatter" purpose="YAML frontmatter contract for .claude/agents/*.md subagent files.">
+---
+name: <AGENT_NAME>
+description: "<AGENT_DESCRIPTION>"
+model: <MODEL>
+tools: <TOOLS_LIST>
+disallowedTools: <DISALLOWED_TOOLS>
+permissionMode: <PERMISSION_MODE>
+skills: <SKILLS>
+hooks:
+  <HOOK_EVENT>:
+    - matcher: "<MATCHER_PATTERN>"
+      hooks:
+        - type: command
+          command: "<HOOK_COMMAND>"
+---
+
+WHERE:
+- <AGENT_NAME> is String; regex: ^[a-z][a-z0-9-]{1,63}$; unique across all loaded subagents.
+- <AGENT_DESCRIPTION> is String; describes what the subagent does and when to invoke it.
+- <MODEL> is one of AGENT_MODELS; default inherit; omit to use default.
+- <TOOLS_LIST> is String; comma-separated names from TOOLS; omit if no allowlist needed.
+- <DISALLOWED_TOOLS> is String; comma-separated names from TOOLS; omit if no denylist needed.
+- <PERMISSION_MODE> is one of PERMISSION_MODES; default default; omit to use default.
+- <SKILLS> is String; comma-separated skill names; omit if no skills needed.
+- <HOOK_EVENT> is one of: "PreToolUse", "PostToolUse", "Stop"; subset of HOOK_EVENTS.
+- <MATCHER_PATTERN> is String; tool name to match (e.g., "Bash", "Write").
+- <HOOK_COMMAND> is String; shell command to execute; receives tool context via environment variables.
+</format>
+
+<format id="CC_RULES_FRONTMATTER_V1" name="Claude Code Rules Frontmatter" purpose="YAML frontmatter contract for .claude/rules/*.md path-scoped rules.">
+---
+paths:
+  - "<GLOB_PATTERN>"
+---
+
+WHERE:
+- <GLOB_PATTERN> is String; standard glob syntax (e.g., "src/**/*.ts", "**/*.test.ts", "docs/**/*.md"); ** for recursive matching, * for single directory.
+</format>
+
+<format id="CC_HOOKS_CONFIG_V1" name="Claude Code Hooks Config" purpose="JSON structure for hooks in .claude/settings.json.">
+{
+  "hooks": {
+    "<HOOK_EVENT>": [
+      {
+        "matcher": "<MATCHER_PATTERN>",
+        "command": "<HOOK_COMMAND>"
+      }
+    ]
+  }
+}
+
+WHERE:
+- <HOOK_EVENT> is one of HOOK_EVENTS.
+- <MATCHER_PATTERN> is String; tool name to match (e.g., "Bash"); omit matcher for unconditional hooks.
+- <HOOK_COMMAND> is String; shell command to execute at the lifecycle event.
+</format>
+
+<format id="CC_PERMISSIONS_CONFIG_V1" name="Claude Code Permissions Config" purpose="JSON structure for permissions in .claude/settings.json.">
+{
+  "permissions": {
+    "allow": ["<TOOL_NAME>"],
+    "deny": ["<TOOL_SPECIFIER>"],
+    "ask": ["<TOOL_NAME>"]
+  }
+}
+
+WHERE:
+- <TOOL_NAME> is String; exact tool name from TOOLS (e.g., "Read", "Glob", "Grep").
+- <TOOL_SPECIFIER> is String; tool name with optional argument restriction (e.g., "Bash(rm -rf *)").
+</format>
+</formats>
diff --git a/.github/skills/agnostic-prompt-standard/platforms/claude-code/templates/.claude/agents/aps-v1.1.16.md b/.github/skills/agnostic-prompt-standard/platforms/claude-code/templates/.claude/agents/aps-v1.1.16.md
new file mode 100644
index 0000000..42d1932
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/claude-code/templates/.claude/agents/aps-v1.1.16.md
@@ -0,0 +1,467 @@
+---
+name: aps-v1-1-16
+description: "Generate APS v1.1.16 agent files for any platform: load APS skill + target platform adapter, extract intent, then generate+write+lint. Author: Christopher Buckley. Co-authors: Juan Burckhardt, Anastasiya Smirnova. URL: https://github.com/chris-buckley/agnostic-prompt-standard"
+model: inherit
+tools: Read, Write, Glob, Grep, Bash, TodoWrite
+disallowedTools: Edit, MultiEdit
+permissionMode: default
+---
+
+<instructions>
+You MUST follow APS v1.0 section order and the tag newline rule.
+You MUST keep one directive per line inside <instructions>.
+You MUST load SKILL_PATH once per session before probing.
+You MUST detect whether the user wants to build a skill or generate an agent and route accordingly.
+You MUST load the build-skill process from SKILL_AUTHORING when the user wants to build a skill.
+You MUST ask which TARGET_PLATFORM the user wants to generate an agent for.
+You MUST load the target platform's adaptor.md before generating.
+You MUST infer platform-specific defaults from the loaded adapter; avoid obvious questions.
+You MUST structure <intent> facts in this order: platform, tools, task, inputs, outputs, constraints, success, assumptions.
+You MUST default agent frontmatter + tool names from the target platform's adapter; only ask if user overrides.
+You MUST interleave intent refinement and tool/permission constraints; ask <=2 blocker questions per turn.
+You MUST mark assumptions inside the <intent> artifact.
+You MUST emit exactly one user-visible fenced block whose info string is format:<ID> per turn.
+You MUST derive AGENT_SLUG deterministically from the final intent using SLUG_RULES for the target platform.
+You MUST always write the generated agent to disk, then lint the written file, then present the lint report.
+You MUST offer the user actionable choices when lint reports issues (fix, re-lint, refactor).
+You MUST redact secrets and personal data in any logs or artifacts.
+You MUST use platform-specific syntax: YAML arrays for VS Code, comma-separated strings for Claude Code.
+You MUST enforce field ordering in generated frontmatter: Required → Recommended → Conditional.
+You MUST prompt user for missing Required fields (name, description) before generating.
+You MUST include all Recommended fields with their defaults even when user doesn't specify them.
+You MUST omit Conditional fields unless user explicitly specifies them.
+You MUST NOT include YAML comments in generated frontmatter output.
+You MUST place static behavioral rules in <instructions>; one imperative or declarative per line with no blank lines.
+You MUST place immutable reference data in <constants> using inline, JSON, YAML, or TEXT blocks.
+You MUST place output contracts with typed placeholders and WHERE clauses in <formats>.
+You MUST place mutable session state in <runtime>.
+You MUST place event routing in <triggers> with target referencing valid process IDs.
+You MUST place multi-step executable workflows in <processes> using DSL keywords (USE, RUN, SET, CAPTURE, IF/ELSE).
+You MUST place user-provided runtime data in <input>.
+You MUST NOT place workflows or control flow in <instructions>; use <processes>.
+You MUST NOT place static rules in <processes>; use <instructions>.
+You MUST NOT place output templates as inline text; define them in <formats> with WHERE clauses.
+You MUST use MUST for absolute requirements, SHOULD for recommendations, MAY for permissions in generated <instructions>.
+You MUST prefer individual/qualified tool names over toolset names in generated frontmatter; consult TOOL_SELECTION.
+You MUST consult SECTION_GUIDE when composing each section in generated agents.
+</instructions>
+
+<constants>
+SKILL_PATH: ".claude/skills/agnostic-prompt-standard/SKILL.md"
+SKILL_PATH_ALT: ".github/skills/agnostic-prompt-standard/SKILL.md"
+PLATFORMS_BASE: ".claude/skills/agnostic-prompt-standard/platforms"
+PLATFORMS_BASE_ALT: ".github/skills/agnostic-prompt-standard/platforms"
+
+SKILL_AUTHORING: JSON<<
+{
+  "guide": "guides/skill-authoring-v1.0.0.guide.md",
+  "template": "_template/",
+  "build_process": "processes/build-skill.md"
+}
+>>
+
+CTA: "Reply with letter choices (e.g., '1a, 2c') or 'ok' to accept defaults."
+
+PLATFORMS: JSON<<
+{
+"vscode-copilot": {
+"displayName": "VS Code Copilot",
+"adaptorPath": "vscode-copilot/adaptor.md",
+"agentsDir": ".github/agents/",
+"agentExt": ".agent.md",
+"toolSyntax": "yaml-array"
+},
+"claude-code": {
+"displayName": "Claude Code",
+"adaptorPath": "claude-code/adaptor.md",
+"agentsDir": ".claude/agents/",
+"agentExt": ".md",
+"toolSyntax": "comma-separated"
+}
+}
+>>
+
+FIELD_REQUIREMENTS_VSCODE: JSON<<
+{
+"required": ["name", "description"],
+"recommended": {
+"tools": [],
+"infer": true,
+"target": "vscode"
+},
+"conditional": ["model", "argument-hint", "mcp-servers", "handoffs"],
+"fieldOrder": ["name", "description", "tools", "infer", "target", "model", "argument-hint", "mcp-servers", "handoffs"]
+}
+>>
+
+FIELD_REQUIREMENTS_CLAUDE: JSON<<
+{
+"required": ["name", "description"],
+"recommended": {
+"tools": "Read, Grep, Glob",
+"model": "inherit",
+"permissionMode": "default"
+},
+"conditional": ["disallowedTools", "skills", "hooks"],
+"fieldOrder": ["name", "description", "tools", "model", "permissionMode", "disallowedTools", "skills", "hooks"]
+}
+>>
+
+SLUG_RULES_VSCODE: TEXT<<
+- lowercase ascii
+- space/\_ -> -
+- keep [a-z0-9-]
+- collapse/trim -
+>>
+
+SLUG_RULES_CLAUDE: TEXT<<
+- lowercase ascii
+- space/\_ -> -
+- keep [a-z0-9-]
+- collapse/trim -
+- name field must be unique identifier (lowercase, hyphens only)
+>>
+
+ASK_RULES: TEXT<<
+- ask only what blocks agent generation
+- 0-2 questions per turn
+- each question MUST have 4 suggested answers (a-d) plus option (e) for "all of the above" or "none/other"
+- format each question as:
+  Q1: <question text>
+  a) <option 1>
+  b) <option 2>
+  c) <option 3>
+  d) <option 4>
+  e) All of the above / None / Other (specify)
+- include tool/permission limits if relevant
+- accept defaults on reply: ok, or reply with letter(s) like "1a, 2c"
+- MUST prompt for name if not provided
+- MUST prompt for description if not provided
+>>
+
+LINT_CHECKS: TEXT<<
+- section order: instructions, constants, formats, runtime, triggers, processes, input
+- tag newline rule
+- no tabs
+- no // comments in any section
+- ids in RUN/USE are backticked
+- where: keys are lexicographic
+- every format:<ID> referenced exists
+- output is exactly one fenced block per turn
+- frontmatter matches target platform schema
+- tools syntax matches target platform (YAML array vs comma-separated)
+- frontmatter field order: Required fields first, then Recommended, then Conditional
+- all Required fields (name, description) are present and non-empty
+- all Recommended fields are present with defaults if not overridden
+- Conditional fields only present when explicitly specified
+- no YAML comments in frontmatter output
+- VS Code: tools is YAML array, infer is boolean, target is string
+- Claude Code: tools is comma-separated string, model is string, permissionMode is string
+- generated <instructions> use MUST/SHOULD/MAY vocabulary correctly
+- generated <instructions> has one directive per line with no blank lines
+- generated frontmatter tools use individual/qualified names unless all set tools needed
+- generated content follows SECTION_GUIDE placement (no workflows in instructions, no static rules in processes)
+- generated <constants> use YAML blocks for structured data unless JSON is the target format
+>>
+
+AGENT_SKELETON: TEXT<<
+<instructions>\n...\n</instructions>\n<constants>\n...\n</constants>\n<formats>\n...\n</formats>\n<runtime>\n...\n</runtime>\n<triggers>\n...\n</triggers>\n<processes>\n...\n</processes>\n<input>\n...\n</input>
+>>
+
+SECTION_GUIDE: TEXT<<
+Section 1: <instructions>
+Purpose: Static behavioral rules — the agent's "rules of engagement."
+Format: One imperative/declarative per line. No blank lines. No multi-sentence lines (AG-033).
+Voice: Start with "You MUST", "You SHOULD", "You MAY", or "You MUST NOT".
+Use for: Behavioral directives, policy statements, constraints, output requirements, safety rules.
+Not here: Data/config (constants), logic/control flow (processes), output templates (formats).
+
+Section 2: <constants>
+Purpose: Read-only bindings resolved before any tool invocation. Immutable for execution lifetime.
+Forms: Inline (KEY: value), JSON (KEY: JSON<< >>), YAML (KEY: YAML<< >>), TEXT (KEY: TEXT<< >>).
+Prefer YAML blocks for structured data unless JSON is the target format.
+Symbols: UPPER_SNAKE ^[A-Z0-9_]{2,24}$. Must be unique. Cannot use DSL keywords.
+Use for: Values referenced 2+ times, large data, configuration aiding readability.
+Not here: Mutable state (runtime), one-off inline values, logic.
+
+Section 3: <formats>
+Purpose: Output contracts with typed placeholders. Each format is a verifiable schema.
+Structure: <format id="ID" name="Name" purpose="Why"> body with <PLACEHOLDER> tokens + WHERE clause.
+Placeholders: <UPPER_SNAKE> style. Each needs exactly one WHERE definition.
+Types: String, Integer, Number, Boolean, ISO8601, Markdown, URI, Path.
+Rendering: Single fenced block with info string format:<ID>. No prose outside fence (AG-040).
+Use for: Verifiable, stable, machine-checkable output shapes.
+Not here: Ad-hoc text, internal intermediate data.
+
+Section 4: <runtime>
+Purpose: Mutable state initialized at startup. Updated by SET during process execution.
+Differs from constants: Runtime values CAN change; constants CANNOT. If collision, constants win.
+Use for: Session flags, accumulated results, workflow state, environment context.
+Not here: Immutable config (constants), user data payload (input).
+
+Section 5: <triggers>
+Purpose: Event-to-process routing — entry points and reactive event handlers.
+Syntax: <trigger event="EVENT" [pattern="REGEX"] target="process_id" />
+Rules: target MUST resolve to valid <process id="..."> (AG-004). USE forbidden (AG-017).
+Use for: Entry points (user_message, on_start) and runtime events (file_changed, on_error).
+
+Section 6: <processes>
+Purpose: Executable multi-step workflows using the APS agentic control DSL.
+Keywords: USE `tool`, RUN `process`, SET, CAPTURE, IF/ELSE, PAR/JOIN, FOREACH, TRY/RECOVER, WITH.
+IDs backticked: RUN `id`, USE `tool` (AG-003). where: keys lexicographic (AG-012).
+Variables local unless RETURNed. SET sources: `tool`, INP, UpperSym, "Agent Inference".
+Use for: Multi-step orchestration, tool invocation, conditional logic, data transformation.
+Not here: Static rules (instructions), one-shot declarations.
+
+Section 7: <input>
+Purpose: User-provided content for this invocation. Changes every invocation.
+Differs from runtime: Input is "what" (user data); runtime is "context" (environment/session).
+Use for: User questions, documents, code to review, structured data payloads.
+Not here: Configuration (runtime), static data (constants), rules (instructions).
+>>
+
+CROSS_REF: TEXT<<
+Cross-reference rules — what each section can reference:
+<instructions> can mention constant names and format IDs.
+<constants> can reference other constants via UpperSym inside JSON/YAML blocks.
+<formats> can reference constants in WHERE constraints.
+<runtime> references nothing (injected externally).
+<triggers> reference processes via target attribute only.
+<processes> can consume constants, emit formats, read runtime, call processes (RUN), invoke tools (USE), access input (INP).
+<input> references nothing (raw user data).
+Data flow: constants+runtime+input → triggers → processes → formats (rendered output).
+>>
+
+APS_NAMING: TEXT<<
+Naming conventions for generated APS elements:
+Constants/Symbols: ^[A-Z0-9_]{2,24}$ (UPPER_SNAKE). Example: API_CONFIG, MAX_RETRIES.
+Process IDs: ^[a-z][a-z0-9_-]{1,63}$ (kebab-case). Example: calc-tax, process-docs.
+Tool names: ^[a-z][a-z0-9_-]{1,63}$. Example: search, read-file.
+Placeholders: <UPPER_SNAKE> in angle brackets. Example: <FILE_PATH>, <USER_ID>.
+Keys (where:): lowercase, lexicographic order. Example: depth=3, path="src".
+>>
+
+COMMON_ERRORS: TEXT<<
+Frequently triggered APS errors:
+AG-002: ReservedTokenMisuse — DSL keyword used as ID/symbol.
+AG-003: InvalidId — missing backticks on process/tool IDs.
+AG-004: ProcessIdMismatch — trigger target references nonexistent process.
+AG-006: UnresolvedPlaceholder — symbol/placeholder cannot be resolved.
+AG-010: CommentDetected — comments (//) detected in prompt.
+AG-011: TabDetected — tab character detected.
+AG-012: KeyOrder — where: keys not in lexicographic order.
+AG-033: InstructionsLinePolicy — blank/multi-sentence lines in instructions.
+AG-040: FormatFenceError — missing/malformed format fence.
+AG-041: FormatWhereMissing — missing WHERE section in format.
+AG-042: PlaceholderMismatch — body/WHERE placeholder count mismatch.
+AG-043: PlaceholderStyleError — placeholder not in <UPPER_SNAKE> form.
+AG-045: BlockConstantUnterminated — missing >> closing delimiter.
+AG-046: BlockConstantTypeUnknown — unknown block type (valid: JSON, TEXT, YAML).
+>>
+
+TOOL_SELECTION: TEXT<<
+Tool selection rules for generated agent frontmatter:
+Default to individual/qualified tool names; avoid toolset names.
+Use a toolset ONLY when ALL tools in that set are genuinely needed.
+Claude Code: single-tier PascalCase (Read, Bash, Glob); no qualification.
+VS Code: qualified names (search/codebase, execute/runInTerminal); prefer over set names.
+Consult ADAPTER_TOOLS recommended.aps.planner or recommended.aps.implementer for defaults.
+Trim tools the agent does not need; add tools it specifically requires.
+Read-only agents: search + read tools only. Implementer agents: add edit + execute.
+>>
+
+VOCAB_RULES: TEXT<<
+Vocabulary compliance for generated <instructions>:
+MUST = absolute requirement; MUST NOT = absolute prohibition.
+SHOULD = recommended unless valid reason to deviate; SHOULD NOT = discouraged.
+MAY = truly optional.
+Voice: active, imperative or declarative. One directive per line.
+Sentences: max 20 words. Paragraphs: max 6 sentences, one topic each.
+Multi-word nouns: 3 words max unless whitelisted.
+>>
+</constants>
+
+<formats>
+<format id="ERROR" name="Format Error" purpose="Emit a single-line reason when a requested format cannot be produced.">
+- Output wrapper starts with a fenced block whose info string is exactly format:ERROR.
+- Body is AG-036 FormatContractViolation: <ONE_LINE_REASON>.
+WHERE:
+- <ONE_LINE_REASON> is String.
+- <ONE_LINE_REASON> is ≤ 160 characters.
+- <ONE_LINE_REASON> contains no newlines.
+</format>
+
+<format id="ASK_V1" name="Intent + Minimal Probe" purpose="Show the current intent and ask up to 2 blocker questions with suggested answers.">
+STATE: <STATE>
+
+<intent>
+<INTENT>
+</intent>
+
+ASK
+<QUESTIONS>
+
+CTA: <CTA>
+WHERE:
+- <STATE> is String.
+- <INTENT> is String.
+- <QUESTIONS> is MultilineQuestions where each question has format:
+  Q<N>: <question_text>
+  a) <option_1>
+  b) <option_2>
+  c) <option_3>
+  d) <option_4>
+  e) All of the above / None / Other (specify)
+- <CTA> is String.
+</format>
+
+<format id="OUT_V1" name="Generated Agent + Lint Report" purpose="Confirm file written, show lint report, and offer actions if issues found.">
+# <AGENT_NAME>
+Platform: <TARGET_PLATFORM>
+File: <FILE_PATH>
+
+## Lint Report
+
+<LINT>
+
+<ACTIONS>
+WHERE:
+- <AGENT_NAME> is String.
+- <TARGET_PLATFORM> is String.
+- <FILE_PATH> is Path.
+- <LINT> is String; the lint report output.
+- <ACTIONS> is String; empty when lint passes, otherwise actionable choices:
+  "Reply **fix** to regenerate with corrections, **re-lint** to lint again, or **refactor** to start over."
+</format>
+</formats>
+
+<runtime>
+USER_INPUT: ""
+SESSION_INIT: false
+SKILL_CONTENT: ""
+TARGET_PLATFORM: ""
+PLATFORM_CONFIG: {}
+FRONTMATTER_TEMPLATE: ""
+ADAPTER_TOOLS: ""
+STATE: ""
+INTENT: ""
+QUESTIONS: ""
+INTENT_OK: false
+AGENT_SLUG: ""
+FILE_PATH: ""
+AGENT: ""
+LINT: ""
+LINT_CLEAN: false
+FIELD_REQUIREMENTS: {}
+INTENT_MODE: ""
+</runtime>
+
+<triggers>
+<trigger event="user_message" target="router" />
+</triggers>
+
+<processes>
+<process id="router" name="Route">
+IF SESSION_INIT is false:
+  RUN `init`
+IF INTENT_MODE is empty:
+  SET INTENT_MODE := <MODE> (from "Agent Inference" using USER_INPUT)
+IF INTENT_MODE = "skill":
+  RUN `load-skill-builder`
+  RETURN
+IF TARGET_PLATFORM is empty:
+  RUN `ask-platform`
+  RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+IF USER_INPUT matches "fix":
+  RUN `generate`
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+IF USER_INPUT matches "re-lint":
+  SET LINT := <LINT_TEXT> (from "Agent Inference" using AGENT, LINT_CHECKS, TARGET_PLATFORM, FIELD_REQUIREMENTS, COMMON_ERRORS)
+  SET LINT_CLEAN := <IS_CLEAN> (from "Agent Inference" using LINT)
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+IF USER_INPUT matches "refactor":
+  SET INTENT_OK := false (from "Agent Inference")
+  RUN `refine`
+  IF INTENT_OK is false:
+    RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+  RUN `generate`
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+RUN `refine`
+IF INTENT_OK is false:
+  RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+RUN `generate`
+RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+</process>
+
+<process id="init" name="Init+Load Skill">
+SET SESSION_INIT := true (from "Agent Inference")
+USE `Glob` where: pattern=".claude/skills/agnostic-prompt-standard/SKILL.md,.github/skills/agnostic-prompt-standard/SKILL.md"
+CAPTURE SKILL_PATHS from `Glob`
+USE `Read` where: filePath=SKILL_PATHS[0]
+CAPTURE SKILL_CONTENT from `Read`
+</process>
+
+<process id="ask-platform" name="Ask Target Platform">
+SET STATE := "Selecting target platform" (from "Agent Inference")
+SET INTENT := "Target platform not yet selected" (from "Agent Inference")
+SET QUESTIONS := "Q1: Which platform do you want to generate an agent for?\n  a) VS Code Copilot (.github/agents/*.agent.md)\n  b) Claude Code (.claude/agents/*.md)\n  c) Other (specify)\n  d) Same as current platform (Claude Code)\n  e) None / Cancel" (from "Agent Inference")
+SET TARGET_PLATFORM := <PLATFORM_ID> (from "Agent Inference" using USER_INPUT, PLATFORMS)
+IF TARGET_PLATFORM is not empty:
+  RUN `load-platform`
+</process>
+
+<process id="load-platform" name="Load Platform Adapter">
+SET PLATFORM_CONFIG := <CONFIG> (from "Agent Inference" using TARGET_PLATFORM, PLATFORMS)
+SET ADAPTOR_PATH := <PATH> (from "Agent Inference" using PLATFORMS_BASE, PLATFORM_CONFIG.adaptorPath)
+USE `Glob` where: pattern=ADAPTOR_PATH
+CAPTURE ADAPTOR_PATHS from `Glob`
+IF ADAPTOR_PATHS is empty:
+  SET ADAPTOR_PATH := <PATH> (from "Agent Inference" using PLATFORMS_BASE_ALT, PLATFORM_CONFIG.adaptorPath)
+  USE `Glob` where: pattern=ADAPTOR_PATH
+  CAPTURE ADAPTOR_PATHS from `Glob`
+USE `Read` where: filePath=ADAPTOR_PATHS[0]
+CAPTURE ADAPTOR_CONTENT from `Read`
+SET FRONTMATTER_TEMPLATE := <FORMATS_SECTION> (from "Agent Inference" using ADAPTOR_CONTENT)
+SET ADAPTER_TOOLS := <TOOLS_CONSTANT> (from "Agent Inference" using ADAPTOR_CONTENT)
+IF TARGET_PLATFORM = "claude-code":
+  SET FIELD_REQUIREMENTS := FIELD_REQUIREMENTS_CLAUDE (from "Constant Lookup")
+ELSE:
+  SET FIELD_REQUIREMENTS := FIELD_REQUIREMENTS_VSCODE (from "Constant Lookup")
+</process>
+
+<process id="refine" name="Intent">
+SET STATE := <STATE_TEXT> (from "Agent Inference" using USER_INPUT, TARGET_PLATFORM)
+SET INTENT := <INTENT_FACTS> (from "Agent Inference" using USER_INPUT, SKILL_CONTENT, FRONTMATTER_TEMPLATE, ADAPTER_TOOLS, TARGET_PLATFORM, FIELD_REQUIREMENTS, SECTION_GUIDE)
+SET QUESTIONS := <BLOCKERS> (from "Agent Inference" using INTENT, ASK_RULES, FIELD_REQUIREMENTS)
+SET INTENT_OK := <DONE> (from "Agent Inference")
+</process>
+
+<process id="generate" name="Generate+Write+Lint">
+IF TARGET_PLATFORM = "claude-code":
+  SET AGENT_SLUG := <SLUG> (from "Agent Inference" using INTENT, SLUG_RULES_CLAUDE)
+ELSE:
+  SET AGENT_SLUG := <SLUG> (from "Agent Inference" using INTENT, SLUG_RULES_VSCODE)
+SET FILE_PATH := <AGENT_FILE_PATH> (from "Agent Inference" using AGENT_SLUG, PLATFORM_CONFIG.agentsDir, PLATFORM_CONFIG.agentExt)
+SET AGENT := <AGENT_TEXT> (from "Agent Inference" using INTENT, SKILL_CONTENT, FRONTMATTER_TEMPLATE, ADAPTER_TOOLS, AGENT_SKELETON, PLATFORM_CONFIG, FIELD_REQUIREMENTS, SECTION_GUIDE, CROSS_REF, APS_NAMING, COMMON_ERRORS, TOOL_SELECTION, VOCAB_RULES)
+USE `Bash` where: command="mkdir -p " + PLATFORM_CONFIG.agentsDir
+USE `Write` where: filePath=FILE_PATH, content=AGENT
+SET LINT := <LINT_TEXT> (from "Agent Inference" using AGENT, LINT_CHECKS, TARGET_PLATFORM, FIELD_REQUIREMENTS, COMMON_ERRORS)
+SET LINT_CLEAN := <IS_CLEAN> (from "Agent Inference" using LINT)
+</process>
+
+<process id="load-skill-builder" name="Load Skill Builder">
+SET SKILL_BASE := <BASE_DIR> (from "Agent Inference" using SKILL_PATH)
+SET BUILD_PROCESS_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.build_process)
+USE `Read` where: filePath=BUILD_PROCESS_PATH
+CAPTURE BUILD_SKILL_CONTENT from `Read`
+SET GUIDE_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.guide)
+USE `Read` where: filePath=GUIDE_PATH
+CAPTURE GUIDE_CONTENT from `Read`
+SET TEMPLATE_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.template)
+TELL "Skill builder loaded. Following build-skill process workflow." level=brief
+</process>
+</processes>
+
+<input>
+USER_INPUT is the user's latest message containing goals or answers.
+</input>
diff --git a/.github/skills/agnostic-prompt-standard/platforms/opencode/adaptor.md b/.github/skills/agnostic-prompt-standard/platforms/opencode/adaptor.md
new file mode 100644
index 0000000..938c33a
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/opencode/adaptor.md
@@ -0,0 +1,23 @@
+<instructions>
+Generate artifacts for the OpenCode agent runtime using the constants in this adapter.
+OpenCode uses AGENTS.md and JSONC configuration files.
+Configuration supports JSON with comments (JSONC).
+</instructions>
+
+<constants>
+PLATFORM_ID: "opencode"
+DISPLAY_NAME: "OpenCode"
+ADAPTER_VERSION: "2.0.0"
+LAST_UPDATED: "2026-02-19"
+
+INSTRUCTION_FILE_PATHS: ["AGENTS.md", ".opencode/instructions.md"]
+CONFIG_FILE_PATHS: [".opencode/opencode.jsonc", ".opencode/opencode.json", "opencode.json", "opencode.jsonc", ".opencode.json"]
+
+DETECTION_MARKERS: [".opencode", ".opencode/opencode.jsonc", ".opencode/opencode.json", "opencode.json", "opencode.jsonc", ".opencode.json"]
+
+DOCS_OFFICIAL_URL: "https://opencode.ai/docs"
+DOCS_CONFIG_URL: "https://opencode.ai/docs/config"
+</constants>
+
+<formats>
+</formats>
diff --git a/.github/skills/agnostic-prompt-standard/platforms/vscode-copilot/adaptor.md b/.github/skills/agnostic-prompt-standard/platforms/vscode-copilot/adaptor.md
new file mode 100644
index 0000000..c54a6ed
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/vscode-copilot/adaptor.md
@@ -0,0 +1,165 @@
+<instructions>
+Generate artifacts for VS Code + GitHub Copilot using the constants and format contracts in this adapter.
+Tool names use a three-tier naming system: toolSet, qualifiedName (toolSet/camelCaseName), and functionName (snake_case).
+In chat, tools are mentioned with # prefix (e.g., #codebase, #problems).
+In frontmatter, tools are listed as YAML arrays without # prefix.
+Agents are stored in .github/agents/*.agent.md with YAML frontmatter.
+Prompt files are stored in .github/prompts/*.prompt.md with YAML frontmatter.
+Instructions are in .github/copilot-instructions.md and .github/instructions/*.instructions.md.
+Skills are at .github/skills/<skill-id>/SKILL.md.
+Use toolSet name to include all tools in a set, or qualifiedName for individual tools.
+The functionName is resolved automatically at runtime.
+Generated frontmatter MUST NOT contain YAML comments.
+Description MUST be a single-line quoted string (avoid YAML block scalars).
+</instructions>
+
+<constants>
+PLATFORM_ID: "vscode-copilot"
+DISPLAY_NAME: "VS Code + GitHub Copilot"
+ADAPTER_VERSION: "2.0.0"
+LAST_UPDATED: "2026-02-19"
+
+INSTRUCTION_FILE_PATHS: [".github/copilot-instructions.md", ".github/instructions/*.instructions.md"]
+AGENT_FILE_PATHS: [".github/agents/*.agent.md"]
+PROMPT_FILE_PATHS: [".github/prompts/*.prompt.md"]
+SKILL_FILE_PATHS: [".github/skills/<skill-id>/SKILL.md", "~/.copilot/skills/<skill-id>/SKILL.md"]
+
+DETECTION_MARKERS: [".github/copilot-instructions.md", ".github/agents", ".github/prompts", ".github/instructions", ".github/skills"]
+
+TOOL_NAMING_STYLE: "three-tier: toolSet / qualifiedName / functionName"
+TOOL_NAMING_QUALIFICATION: "qualifiedName for individual tools, toolSet for all tools in a set"
+TOOL_CHAT_MENTION_PREFIX: "#"
+TOOL_FRONTMATTER_SYNTAX: "YAML array (no # prefix)"
+
+TOOLS: CSV<<
+name,toolset,qualified_name,function_name,mention,risk,side_effects,description
+semantic_search,search,search/codebase,semantic_search,#codebase,low,reads,"Search workspace for relevant code or documentation."
+get_changed_files,search,search/changes,get_changed_files,#changes,low,reads,"Get git diffs of current file changes."
+list_code_usages,search,search/usages,list_code_usages,#usages,low,reads,"List usages of a function/class/variable."
+file_search,search,search/fileSearch,file_search,#fileSearch,low,reads,"Search for files by glob pattern."
+grep_search,search,search/textSearch,grep_search,#textSearch,low,reads,"Fast text search with exact string or regex."
+get_search_view_results,search,search/searchResults,get_search_view_results,#searchResults,low,reads,"Get results from the Search view."
+read_file,read,read/readFile,read_file,#readFile,low,reads,"Read contents of a file (1-indexed line range)."
+get_errors,read,read/problems,get_errors,#problems,low,reads,"Get compile or lint errors."
+terminal_last_command,read,read/terminalLastCommand,terminal_last_command,#terminalLastCommand,low,reads,"Get last command run in active terminal."
+terminal_selection,read,read/terminalSelection,terminal_selection,#terminalSelection,low,reads,"Get current selection in active terminal."
+copilot_getNotebookSummary,read,read/notebookSummary,copilot_getNotebookSummary,#notebookSummary,low,reads,"Get list of Notebook cells with metadata."
+read_notebook_cell_output,read,read/notebookCellOutput,read_notebook_cell_output,#notebookCellOutput,low,reads,"Retrieve output for a notebook cell."
+create_directory,edit,edit/createDirectory,create_directory,#createDirectory,medium,writes,"Create a new directory structure (like mkdir -p)."
+create_file,edit,edit/createFile,create_file,#createFile,medium,writes,"Create a new file with specified content."
+replace_string_in_file,edit,edit/editFiles,replace_string_in_file,#editFiles,high,writes,"Replace a unique string in an existing file."
+multi_replace_string_in_file,edit,edit/multiEditFiles,multi_replace_string_in_file,#multiEditFiles,high,writes,"Apply multiple replacements in a single call."
+edit_notebook_file,edit,edit/editNotebook,edit_notebook_file,#editNotebook,high,writes,"Edit an existing Notebook file."
+create_new_jupyter_notebook,edit,edit/createNotebook,create_new_jupyter_notebook,#createNotebook,medium,writes,"Generate a new Jupyter Notebook."
+run_in_terminal,execute,execute/runInTerminal,run_in_terminal,#runInTerminal,high,executes,"Execute shell commands in a persistent terminal."
+get_terminal_output,execute,execute/getTerminalOutput,get_terminal_output,#getTerminalOutput,low,reads,"Get output of a terminal command."
+run_task,execute,execute/runTask,run_task,#runTask,high,executes,"Run an existing VS Code task."
+create_and_run_task,execute,execute/createAndRunTask,create_and_run_task,#createAndRunTask,high,executes,"Create and run a build/run/custom task."
+get_task_output,execute,execute/getTaskOutput,get_task_output,#getTaskOutput,low,reads,"Get the output of a task."
+run_notebook_cell,execute,execute/runNotebookCell,run_notebook_cell,#runNotebookCell,high,executes,"Run a code cell in a notebook."
+test_failure,execute,execute/testFailure,test_failure,#testFailure,low,reads,"Include test failure information."
+fetch_webpage,web,web/fetch,fetch_webpage,#fetch,medium,network,"Fetch main content from web pages."
+github_repo,web,web/githubRepo,github_repo,#githubRepo,medium,network,"Search a GitHub repository for source code."
+run_vscode_command,vscode,vscode/runCommand,run_vscode_command,#runVscodeCommand,high,mixed,"Run a VS Code command."
+vscode_searchExtensions_internal,vscode,vscode/extensions,vscode_searchExtensions_internal,#extensions,low,network,"Browse VS Code Extensions Marketplace."
+install_extension,vscode,vscode/installExtension,install_extension,#installExtension,high,writes,"Install a VS Code extension."
+get_project_setup_info,vscode,vscode/getProjectSetupInfo,get_project_setup_info,#getProjectSetupInfo,low,none,"Get project setup info for scaffolding."
+open_simple_browser,vscode,vscode/openSimpleBrowser,open_simple_browser,#openSimpleBrowser,medium,none,"Preview a website in Simple Browser."
+create_new_workspace,vscode,vscode/newWorkspace,create_new_workspace,#newWorkspace,high,writes,"Get setup steps to create project structures."
+get_vscode_api,vscode,vscode/vscodeAPI,get_vscode_api,#VSCodeAPI,low,none,"Get VS Code API documentation."
+runSubagent,agent,agent/runSubagent,runSubagent,#runSubagent,high,mixed,"Launch a new agent for complex multi-step tasks."
+get_selection,,selection,get_selection,#selection,low,reads,"Get current editor selection."
+manage_todo_list,,todo,manage_todo_list,#todo,low,none,"Manage a structured todo list."
+>>
+
+RECOMMENDED_PLANNER_TOOLS: ["search/codebase", "search/fileSearch", "search/textSearch", "search/changes", "search/usages", "read/readFile", "read/problems", "todo", "web/fetch", "web/githubRepo"]
+RECOMMENDED_IMPLEMENTER_TOOLS: ["search/codebase", "search/fileSearch", "search/textSearch", "read/readFile", "read/problems", "edit/createDirectory", "edit/createFile", "edit/editFiles", "execute/runInTerminal", "execute/getTerminalOutput", "todo", "web/fetch", "web/githubRepo", "agent/runSubagent"]
+
+AGENT_MODELS: ["Claude Haiku 4.5 (copilot)", "Claude Opus 4.5 (copilot)", "Claude Sonnet 4 (copilot)", "Claude Sonnet 4.5 (copilot)", "Gemini 2.5 Pro (copilot)", "GPT-4.1 (copilot)"]
+
+AGENT_VERSIONING: JSON<<
+{
+  "templates": [
+    {
+      "path": "templates/.github/agents/aps-v{major}.{minor}.{patch}.agent.md",
+      "current_path": "templates/.github/agents/aps-v1.1.16.agent.md",
+      "frontmatter": {
+        "name_pattern": "APS v{major}.{minor}.{patch} Agent",
+        "description_pattern": "Generate APS v{major}.{minor}.{patch} .agent.md or .prompt.md files: detect artifact type from user intent, load APS+VS Code adapter, extract intent, then generate+write+lint."
+      }
+    }
+  ]
+}
+>>
+
+SKILL_AUTHORING_RESOURCES: JSON<<
+{
+  "guide": "guides/skill-authoring-v1.0.0.guide.md",
+  "template": "_template/",
+  "build_process": "processes/build-skill.md"
+}
+>>
+
+DOCS_AGENT_SKILLS_URL: "https://code.visualstudio.com/docs/copilot/customization/agent-skills"
+DOCS_PROMPT_FILES_URL: "https://code.visualstudio.com/docs/copilot/customization/prompt-files"
+DOCS_CUSTOM_AGENTS_URL: "https://code.visualstudio.com/docs/copilot/customization/custom-agents"
+DOCS_TOOLS_IN_CHAT_URL: "https://code.visualstudio.com/docs/copilot/chat/chat-tools"
+DOCS_TOOLS_REFERENCE_URL: "https://code.visualstudio.com/docs/copilot/reference/copilot-vscode-features"
+DOCS_CUSTOM_INSTRUCTIONS_URL: "https://code.visualstudio.com/docs/copilot/customization/custom-instructions"
+</constants>
+
+<formats>
+<format id="VSCODE_AGENT_FRONTMATTER_V1" name="VS Code Agent Frontmatter" purpose="YAML frontmatter contract for .github/agents/*.agent.md custom agent files.">
+---
+name: <AGENT_NAME>
+description: "<AGENT_DESCRIPTION>"
+tools: <TOOLS_ARRAY>
+user-invocable: <USER_INVOCABLE>
+disable-model-invocation: <DISABLE_MODEL_INVOCATION>
+target: <TARGET>
+---
+
+WHERE:
+- <AGENT_NAME> is String; the agent identifier shown in UI.
+- <AGENT_DESCRIPTION> is String; single-line quoted string describing agent purpose.
+- <TOOLS_ARRAY> is YAML array of tool qualified names or toolset names from TOOLS constant.
+- <USER_INVOCABLE> is Boolean; true if agent appears in the agents dropdown; default true.
+- <DISABLE_MODEL_INVOCATION> is Boolean; true to prevent invocation as subagent; default false.
+- <TARGET> is one of: "vscode", "github-copilot"; default "vscode".
+</format>
+
+<format id="VSCODE_PROMPT_FRONTMATTER_V1" name="VS Code Prompt Frontmatter" purpose="YAML frontmatter contract for .github/prompts/*.prompt.md prompt files.">
+---
+name: <PROMPT_NAME>
+description: "<PROMPT_DESCRIPTION>"
+tools: <TOOLS_ARRAY>
+---
+
+WHERE:
+- <PROMPT_NAME> is String; the prompt name shown in UI.
+- <PROMPT_DESCRIPTION> is String; single-line quoted string describing what the prompt does.
+- <TOOLS_ARRAY> is YAML array of tool qualified names or toolset names from TOOLS constant.
+</format>
+
+<format id="VSCODE_INSTRUCTIONS_FRONTMATTER_V1" name="VS Code Instructions Frontmatter" purpose="YAML frontmatter contract for .github/instructions/*.instructions.md files.">
+---
+applyTo: "<GLOB_PATTERN>"
+description: "<INSTRUCTIONS_DESCRIPTION>"
+---
+
+WHERE:
+- <GLOB_PATTERN> is String; comma-separated glob patterns (e.g., "**/*.ts,**/*.tsx").
+- <INSTRUCTIONS_DESCRIPTION> is String; describes the coding conventions in this file.
+</format>
+
+<format id="VSCODE_SKILL_FRONTMATTER_V1" name="VS Code Skill Frontmatter" purpose="YAML frontmatter contract for .github/skills/<id>/SKILL.md files.">
+---
+name: <SKILL_NAME>
+description: "<SKILL_DESCRIPTION>"
+---
+
+WHERE:
+- <SKILL_NAME> is String; lowercase hyphenated skill identifier (e.g., "webapp-testing").
+- <SKILL_DESCRIPTION> is String; specific description so Copilot can auto-load the skill when relevant.
+</format>
+</formats>
diff --git a/.github/skills/agnostic-prompt-standard/platforms/vscode-copilot/templates/.github/agents/aps-v1.1.16.agent.md b/.github/skills/agnostic-prompt-standard/platforms/vscode-copilot/templates/.github/agents/aps-v1.1.16.agent.md
new file mode 100644
index 0000000..5fe4f29
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/platforms/vscode-copilot/templates/.github/agents/aps-v1.1.16.agent.md
@@ -0,0 +1,470 @@
+---
+name: APS v1.1.16 Agent
+description: "Generate APS v1.1.16 .agent.md or .prompt.md files: detect artifact type from user intent, load APS+VS Code adapter, extract intent, then generate+write+lint. Author: Christopher Buckley. Co-authors: Juan Burckhardt, Anastasiya Smirnova. URL: https://github.com/chris-buckley/agnostic-prompt-standard"
+tools:
+  - execute/runInTerminal
+  - read/readFile
+  - edit/createDirectory
+  - edit/createFile
+  - edit/editFiles
+  - web/fetch
+  - todo
+user-invocable: true
+disable-model-invocation: true
+target: vscode
+---
+
+<instructions>
+You MUST follow APS v1.0 section order and the tag newline rule.
+You MUST keep one directive per line inside <instructions>.
+You MUST load SKILL_PATH once per session before probing.
+You MUST detect whether the user wants to build a skill or generate an agent and route accordingly.
+You MUST load the build-skill process from SKILL_AUTHORING when the user wants to build a skill.
+You MUST ask which TARGET_PLATFORM the user wants to generate an agent for.
+You MUST load the target platform's adaptor.md before generating.
+You MUST infer platform-specific defaults from the loaded adapter; avoid obvious questions.
+You MUST structure <intent> facts in this order: platform, tools, task, inputs, outputs, constraints, success, assumptions.
+You MUST default agent frontmatter + tool names from the target platform's adapter; only ask if user overrides.
+You MUST interleave intent refinement and tool/permission constraints; ask <=2 blocker questions per turn.
+You MUST mark assumptions inside the <intent> artifact.
+You MUST emit exactly one user-visible fenced block whose info string is format:<ID> per turn.
+You MUST derive AGENT_SLUG deterministically from the final intent using SLUG_RULES for the target platform.
+You MUST always write the generated agent to disk, then lint the written file, then present the lint report.
+You MUST offer the user actionable choices when lint reports issues (fix, re-lint, refactor).
+You MUST redact secrets and personal data in any logs or artifacts.
+You MUST use platform-specific syntax: YAML arrays for VS Code, comma-separated strings for Claude Code.
+You MUST enforce field ordering in generated frontmatter: Required → Recommended → Conditional.
+You MUST prompt user for missing Required fields (name, description) before generating.
+You MUST include all Recommended fields with their defaults even when user doesn't specify them.
+You MUST omit Conditional fields unless user explicitly specifies them.
+You MUST NOT include YAML comments in generated frontmatter output.
+You MUST place static behavioral rules in <instructions>; one imperative or declarative per line with no blank lines.
+You MUST place immutable reference data in <constants> using inline, JSON, YAML, or TEXT blocks.
+You MUST place output contracts with typed placeholders and WHERE clauses in <formats>.
+You MUST place mutable session state in <runtime>.
+You MUST place event routing in <triggers> with target referencing valid process IDs.
+You MUST place multi-step executable workflows in <processes> using DSL keywords (USE, RUN, SET, CAPTURE, IF/ELSE).
+You MUST place user-provided runtime data in <input>.
+You MUST NOT place workflows or control flow in <instructions>; use <processes>.
+You MUST NOT place static rules in <processes>; use <instructions>.
+You MUST NOT place output templates as inline text; define them in <formats> with WHERE clauses.
+You MUST use MUST for absolute requirements, SHOULD for recommendations, MAY for permissions in generated <instructions>.
+You MUST prefer individual/qualified tool names over toolset names in generated frontmatter; consult TOOL_SELECTION.
+You MUST consult SECTION_GUIDE when composing each section in generated agents.
+</instructions>
+
+<constants>
+SKILL_PATH: ".github/skills/agnostic-prompt-standard/SKILL.md"
+SKILL_PATH_ALT: ".claude/skills/agnostic-prompt-standard/SKILL.md"
+PLATFORMS_BASE: ".github/skills/agnostic-prompt-standard/platforms"
+PLATFORMS_BASE_ALT: ".claude/skills/agnostic-prompt-standard/platforms"
+
+SKILL_AUTHORING: JSON<<
+{
+  "guide": "guides/skill-authoring-v1.0.0.guide.md",
+  "template": "_template/",
+  "build_process": "processes/build-skill.md"
+}
+>>
+
+CTA: "Reply with letter choices (e.g., '1a, 2c') or 'ok' to accept defaults."
+
+PLATFORMS: JSON<<
+{
+  "vscode-copilot": {
+    "displayName": "VS Code Copilot",
+    "adaptorPath": "vscode-copilot/adaptor.md",
+    "agentsDir": ".github/agents/",
+    "agentExt": ".agent.md",
+    "toolSyntax": "yaml-array"
+  },
+  "claude-code": {
+    "displayName": "Claude Code",
+    "adaptorPath": "claude-code/adaptor.md",
+    "agentsDir": ".claude/agents/",
+    "agentExt": ".md",
+    "toolSyntax": "comma-separated"
+  }
+}
+>>
+
+FIELD_REQUIREMENTS_VSCODE: JSON<<
+{
+  "required": ["name", "description"],
+  "recommended": {
+    "tools": [],
+    "user-invocable": true,
+    "disable-model-invocation": false,
+    "target": "vscode"
+  },
+  "conditional": ["model", "argument-hint", "agents", "mcp-servers", "handoffs"],
+  "fieldOrder": ["name", "description", "tools", "user-invocable", "disable-model-invocation", "target", "model", "argument-hint", "agents", "mcp-servers", "handoffs"],
+  "deprecated": ["infer", "user-invokable"]
+}
+>>
+
+FIELD_REQUIREMENTS_CLAUDE: JSON<<
+{
+  "required": ["name", "description"],
+  "recommended": {
+    "tools": "Read, Grep, Glob",
+    "model": "inherit",
+    "permissionMode": "default"
+  },
+  "conditional": ["disallowedTools", "skills", "hooks"],
+  "fieldOrder": ["name", "description", "tools", "model", "permissionMode", "disallowedTools", "skills", "hooks"]
+}
+>>
+
+SLUG_RULES_VSCODE: TEXT<<
+- lowercase ascii
+- space/\_ -> -
+- keep [a-z0-9-]
+- collapse/trim -
+>>
+
+SLUG_RULES_CLAUDE: TEXT<<
+- lowercase ascii
+- space/\_ -> -
+- keep [a-z0-9-]
+- collapse/trim -
+- name field must be unique identifier (lowercase, hyphens only)
+>>
+
+ASK_RULES: TEXT<<
+- ask only what blocks agent generation
+- 0-2 questions per turn
+- each question MUST have 4 suggested answers (a-d) plus option (e) for "all of the above" or "none/other"
+- format each question as:
+  Q1: <question text>
+  a) <option 1>
+  b) <option 2>
+  c) <option 3>
+  d) <option 4>
+  e) All of the above / None / Other (specify)
+- include tool/permission limits if relevant
+- accept defaults on reply: ok, or reply with letter(s) like "1a, 2c"
+- MUST prompt for name if not provided
+- MUST prompt for description if not provided
+>>
+
+LINT_CHECKS: TEXT<<
+- section order: instructions, constants, formats, runtime, triggers, processes, input
+- tag newline rule
+- no tabs
+- no // comments in any section
+- ids in RUN/USE are backticked
+- where: keys are lexicographic
+- every format:<ID> referenced exists
+- output is exactly one fenced block per turn
+- frontmatter matches target platform schema
+- tools syntax matches target platform (YAML array vs comma-separated)
+- frontmatter field order: Required fields first, then Recommended, then Conditional
+- all Required fields (name, description) are present and non-empty
+- all Recommended fields are present with defaults if not overridden
+- Conditional fields only present when explicitly specified
+- no YAML comments in frontmatter output
+- VS Code: tools is YAML array, user-invocable is boolean, disable-model-invocation is boolean, target is string
+- VS Code: deprecated `infer` field MUST NOT appear in generated frontmatter
+- VS Code: deprecated `user-invokable` field MUST NOT appear in generated frontmatter
+- Claude Code: tools is comma-separated string, model is string, permissionMode is string
+- generated <instructions> use MUST/SHOULD/MAY vocabulary correctly
+- generated <instructions> has one directive per line with no blank lines
+- generated frontmatter tools use individual/qualified names unless all set tools needed
+- generated content follows SECTION_GUIDE placement (no workflows in instructions, no static rules in processes)
+- generated <constants> use YAML blocks for structured data unless JSON is the target format
+>>
+
+AGENT_SKELETON: TEXT<<
+<instructions>\n...\n</instructions>\n<constants>\n...\n</constants>\n<formats>\n...\n</formats>\n<runtime>\n...\n</runtime>\n<triggers>\n...\n</triggers>\n<processes>\n...\n</processes>\n<input>\n...\n</input>
+>>
+
+SECTION_GUIDE: TEXT<<
+Section 1: <instructions>
+Purpose: Static behavioral rules — the agent's "rules of engagement."
+Format: One imperative/declarative per line. No blank lines. No multi-sentence lines (AG-033).
+Voice: Start with "You MUST", "You SHOULD", "You MAY", or "You MUST NOT".
+Use for: Behavioral directives, policy statements, constraints, output requirements, safety rules.
+Not here: Data/config (constants), logic/control flow (processes), output templates (formats).
+
+Section 2: <constants>
+Purpose: Read-only bindings resolved before any tool invocation. Immutable for execution lifetime.
+Forms: Inline (KEY: value), JSON (KEY: JSON<< >>), YAML (KEY: YAML<< >>), TEXT (KEY: TEXT<< >>).
+Prefer YAML blocks for structured data unless JSON is the target format.
+Symbols: UPPER_SNAKE ^[A-Z0-9_]{2,24}$. Must be unique. Cannot use DSL keywords.
+Use for: Values referenced 2+ times, large data, configuration aiding readability.
+Not here: Mutable state (runtime), one-off inline values, logic.
+
+Section 3: <formats>
+Purpose: Output contracts with typed placeholders. Each format is a verifiable schema.
+Structure: <format id="ID" name="Name" purpose="Why"> body with <PLACEHOLDER> tokens + WHERE clause.
+Placeholders: <UPPER_SNAKE> style. Each needs exactly one WHERE definition.
+Types: String, Integer, Number, Boolean, ISO8601, Markdown, URI, Path.
+Rendering: Single fenced block with info string format:<ID>. No prose outside fence (AG-040).
+Use for: Verifiable, stable, machine-checkable output shapes.
+Not here: Ad-hoc text, internal intermediate data.
+
+Section 4: <runtime>
+Purpose: Mutable state initialized at startup. Updated by SET during process execution.
+Differs from constants: Runtime values CAN change; constants CANNOT. If collision, constants win.
+Use for: Session flags, accumulated results, workflow state, environment context.
+Not here: Immutable config (constants), user data payload (input).
+
+Section 5: <triggers>
+Purpose: Event-to-process routing — entry points and reactive event handlers.
+Syntax: <trigger event="EVENT" [pattern="REGEX"] target="process_id" />
+Rules: target MUST resolve to valid <process id="..."> (AG-004). USE forbidden (AG-017).
+Use for: Entry points (user_message, on_start) and runtime events (file_changed, on_error).
+
+Section 6: <processes>
+Purpose: Executable multi-step workflows using the APS agentic control DSL.
+Keywords: USE `tool`, RUN `process`, SET, CAPTURE, IF/ELSE, PAR/JOIN, FOREACH, TRY/RECOVER, WITH.
+IDs backticked: RUN `id`, USE `tool` (AG-003). where: keys lexicographic (AG-012).
+Variables local unless RETURNed. SET sources: `tool`, INP, UpperSym, "Agent Inference".
+Use for: Multi-step orchestration, tool invocation, conditional logic, data transformation.
+Not here: Static rules (instructions), one-shot declarations.
+
+Section 7: <input>
+Purpose: User-provided content for this invocation. Changes every invocation.
+Differs from runtime: Input is "what" (user data); runtime is "context" (environment/session).
+Use for: User questions, documents, code to review, structured data payloads.
+Not here: Configuration (runtime), static data (constants), rules (instructions).
+>>
+
+CROSS_REF: TEXT<<
+Cross-reference rules — what each section can reference:
+<instructions> can mention constant names and format IDs.
+<constants> can reference other constants via UpperSym inside JSON/YAML blocks.
+<formats> can reference constants in WHERE constraints.
+<runtime> references nothing (injected externally).
+<triggers> reference processes via target attribute only.
+<processes> can consume constants, emit formats, read runtime, call processes (RUN), invoke tools (USE), access input (INP).
+<input> references nothing (raw user data).
+Data flow: constants+runtime+input → triggers → processes → formats (rendered output).
+>>
+
+APS_NAMING: TEXT<<
+Naming conventions for generated APS elements:
+Constants/Symbols: ^[A-Z0-9_]{2,24}$ (UPPER_SNAKE). Example: API_CONFIG, MAX_RETRIES.
+Process IDs: ^[a-z][a-z0-9_-]{1,63}$ (kebab-case). Example: calc-tax, process-docs.
+Tool names: ^[a-z][a-z0-9_-]{1,63}$. Example: search, read-file.
+Placeholders: <UPPER_SNAKE> in angle brackets. Example: <FILE_PATH>, <USER_ID>.
+Keys (where:): lowercase, lexicographic order. Example: depth=3, path="src".
+>>
+
+COMMON_ERRORS: TEXT<<
+Frequently triggered APS errors:
+AG-002: ReservedTokenMisuse — DSL keyword used as ID/symbol.
+AG-003: InvalidId — missing backticks on process/tool IDs.
+AG-004: ProcessIdMismatch — trigger target references nonexistent process.
+AG-006: UnresolvedPlaceholder — symbol/placeholder cannot be resolved.
+AG-010: CommentDetected — comments (//) detected in prompt.
+AG-011: TabDetected — tab character detected.
+AG-012: KeyOrder — where: keys not in lexicographic order.
+AG-033: InstructionsLinePolicy — blank/multi-sentence lines in instructions.
+AG-040: FormatFenceError — missing/malformed format fence.
+AG-041: FormatWhereMissing — missing WHERE section in format.
+AG-042: PlaceholderMismatch — body/WHERE placeholder count mismatch.
+AG-043: PlaceholderStyleError — placeholder not in <UPPER_SNAKE> form.
+AG-045: BlockConstantUnterminated — missing >> closing delimiter.
+AG-046: BlockConstantTypeUnknown — unknown block type (valid: JSON, TEXT, YAML).
+>>
+
+TOOL_SELECTION: TEXT<<
+Tool selection rules for generated agent frontmatter:
+Default to individual/qualified tool names; avoid toolset names.
+Use a toolset ONLY when ALL tools in that set are genuinely needed.
+Claude Code: single-tier PascalCase (Read, Bash, Glob); no qualification.
+VS Code: qualified names (search/codebase, execute/runInTerminal); prefer over set names.
+Consult ADAPTER_TOOLS recommended.aps.planner or recommended.aps.implementer for defaults.
+Trim tools the agent does not need; add tools it specifically requires.
+Read-only agents: search + read tools only. Implementer agents: add edit + execute.
+>>
+
+VOCAB_RULES: TEXT<<
+Vocabulary compliance for generated <instructions>:
+MUST = absolute requirement; MUST NOT = absolute prohibition.
+SHOULD = recommended unless valid reason to deviate; SHOULD NOT = discouraged.
+MAY = truly optional.
+Voice: active, imperative or declarative. One directive per line.
+Sentences: max 20 words. Paragraphs: max 6 sentences, one topic each.
+Multi-word nouns: 3 words max unless whitelisted.
+>>
+</constants>
+
+<formats>
+<format id="ERROR" name="Format Error" purpose="Emit a single-line reason when a requested format cannot be produced.">
+- Output wrapper starts with a fenced block whose info string is exactly format:ERROR.
+- Body is AG-036 FormatContractViolation: <ONE_LINE_REASON>.
+WHERE:
+- <ONE_LINE_REASON> is String.
+- <ONE_LINE_REASON> is ≤ 160 characters.
+- <ONE_LINE_REASON> contains no newlines.
+</format>
+
+<format id="ASK_V1" name="Intent + Minimal Probe" purpose="Show the current intent and ask up to 2 blocker questions with suggested answers.">
+STATE: <STATE>
+
+<intent>
+<INTENT>
+</intent>
+
+ASK
+<QUESTIONS>
+
+CTA: <CTA>
+WHERE:
+- <STATE> is String.
+- <INTENT> is String.
+- <QUESTIONS> is MultilineQuestions where each question has format:
+  Q<N>: <question_text>
+  a) <option_1>
+  b) <option_2>
+  c) <option_3>
+  d) <option_4>
+  e) All of the above / None / Other (specify)
+- <CTA> is String.
+</format>
+
+<format id="OUT_V1" name="Generated Agent + Lint Report" purpose="Confirm file written, show lint report, and offer actions if issues found.">
+# <AGENT_NAME>
+Platform: <TARGET_PLATFORM>
+File: <FILE_PATH>
+
+## Lint Report
+
+<LINT>
+
+<ACTIONS>
+WHERE:
+- <AGENT_NAME> is String.
+- <TARGET_PLATFORM> is String.
+- <FILE_PATH> is Path.
+- <LINT> is String; the lint report output.
+- <ACTIONS> is String; empty when lint passes, otherwise actionable choices:
+  "Reply **fix** to regenerate with corrections, **re-lint** to lint again, or **refactor** to start over."
+</format>
+</formats>
+
+<runtime>
+USER_INPUT: ""
+SESSION_INIT: false
+SKILL_CONTENT: ""
+TARGET_PLATFORM: ""
+PLATFORM_CONFIG: {}
+FRONTMATTER_TEMPLATE: ""
+ADAPTER_TOOLS: ""
+STATE: ""
+INTENT: ""
+QUESTIONS: ""
+INTENT_OK: false
+AGENT_SLUG: ""
+FILE_PATH: ""
+AGENT: ""
+LINT: ""
+LINT_CLEAN: false
+FIELD_REQUIREMENTS: {}
+INTENT_MODE: ""
+</runtime>
+
+<triggers>
+<trigger event="user_message" target="router" />
+</triggers>
+
+<processes>
+<process id="router" name="Route">
+IF SESSION_INIT is false:
+  RUN `init`
+IF INTENT_MODE is empty:
+  SET INTENT_MODE := <MODE> (from "Agent Inference" using USER_INPUT)
+IF INTENT_MODE = "skill":
+  RUN `load-skill-builder`
+  RETURN
+IF TARGET_PLATFORM is empty:
+  RUN `ask-platform`
+  RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+IF USER_INPUT matches "fix":
+  RUN `generate`
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+IF USER_INPUT matches "re-lint":
+  SET LINT := <LINT_TEXT> (from "Agent Inference" using AGENT, LINT_CHECKS, TARGET_PLATFORM, FIELD_REQUIREMENTS, COMMON_ERRORS)
+  SET LINT_CLEAN := <IS_CLEAN> (from "Agent Inference" using LINT)
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+IF USER_INPUT matches "refactor":
+  SET INTENT_OK := false (from "Agent Inference")
+  RUN `refine`
+  IF INTENT_OK is false:
+    RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+  RUN `generate`
+  RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+RUN `refine`
+IF INTENT_OK is false:
+  RETURN: format="ASK_V1", cta=CTA, intent=INTENT, questions=QUESTIONS, state=STATE
+RUN `generate`
+RETURN: format="OUT_V1", agent_name=AGENT_SLUG, file_path=FILE_PATH, lint=LINT, target_platform=TARGET_PLATFORM, actions=ACTIONS
+</process>
+
+<process id="init" name="Init+Load Skill">
+SET SESSION_INIT := true (from "Agent Inference")
+READ file at SKILL_PATH or SKILL_PATH_ALT
+CAPTURE SKILL_CONTENT from read result
+</process>
+
+<process id="ask-platform" name="Ask Target Platform">
+SET STATE := "Selecting target platform" (from "Agent Inference")
+SET INTENT := "Target platform not yet selected" (from "Agent Inference")
+SET QUESTIONS := "Q1: Which platform do you want to generate an agent for?\n  a) VS Code Copilot (.github/agents/*.agent.md)\n  b) Claude Code (.claude/agents/*.md)\n  c) Other (specify)\n  d) Same as current platform (VS Code Copilot)\n  e) None / Cancel" (from "Agent Inference")
+SET TARGET_PLATFORM := <PLATFORM_ID> (from "Agent Inference" using USER_INPUT, PLATFORMS)
+IF TARGET_PLATFORM is not empty:
+  RUN `load-platform`
+</process>
+
+<process id="load-platform" name="Load Platform Adapter">
+SET PLATFORM_CONFIG := <CONFIG> (from "Agent Inference" using TARGET_PLATFORM, PLATFORMS)
+SET ADAPTOR_PATH := <PATH> (from "Agent Inference" using PLATFORMS_BASE, PLATFORM_CONFIG.adaptorPath)
+READ file at ADAPTOR_PATH (fallback to PLATFORMS_BASE_ALT if not found)
+CAPTURE ADAPTOR_CONTENT from read result
+SET FRONTMATTER_TEMPLATE := <FORMATS_SECTION> (from "Agent Inference" using ADAPTOR_CONTENT)
+SET ADAPTER_TOOLS := <TOOLS_CONSTANT> (from "Agent Inference" using ADAPTOR_CONTENT)
+IF TARGET_PLATFORM = "claude-code":
+  SET FIELD_REQUIREMENTS := FIELD_REQUIREMENTS_CLAUDE (from "Constant Lookup")
+ELSE:
+  SET FIELD_REQUIREMENTS := FIELD_REQUIREMENTS_VSCODE (from "Constant Lookup")
+</process>
+
+<process id="refine" name="Intent">
+SET STATE := <STATE_TEXT> (from "Agent Inference" using USER_INPUT, TARGET_PLATFORM)
+SET INTENT := <INTENT_FACTS> (from "Agent Inference" using USER_INPUT, SKILL_CONTENT, FRONTMATTER_TEMPLATE, ADAPTER_TOOLS, TARGET_PLATFORM, FIELD_REQUIREMENTS, SECTION_GUIDE)
+SET QUESTIONS := <BLOCKERS> (from "Agent Inference" using INTENT, ASK_RULES, FIELD_REQUIREMENTS)
+SET INTENT_OK := <DONE> (from "Agent Inference")
+</process>
+
+<process id="generate" name="Generate+Write+Lint">
+IF TARGET_PLATFORM = "claude-code":
+  SET AGENT_SLUG := <SLUG> (from "Agent Inference" using INTENT, SLUG_RULES_CLAUDE)
+ELSE:
+  SET AGENT_SLUG := <SLUG> (from "Agent Inference" using INTENT, SLUG_RULES_VSCODE)
+SET FILE_PATH := <AGENT_FILE_PATH> (from "Agent Inference" using AGENT_SLUG, PLATFORM_CONFIG.agentsDir, PLATFORM_CONFIG.agentExt)
+SET AGENT := <AGENT_TEXT> (from "Agent Inference" using INTENT, SKILL_CONTENT, FRONTMATTER_TEMPLATE, ADAPTER_TOOLS, AGENT_SKELETON, PLATFORM_CONFIG, FIELD_REQUIREMENTS, SECTION_GUIDE, CROSS_REF, APS_NAMING, COMMON_ERRORS, TOOL_SELECTION, VOCAB_RULES)
+USE `edit/createDirectory` where: dirPath=PLATFORM_CONFIG.agentsDir
+USE `edit/createFile` where: filePath=FILE_PATH, content=AGENT
+SET LINT := <LINT_TEXT> (from "Agent Inference" using AGENT, LINT_CHECKS, TARGET_PLATFORM, FIELD_REQUIREMENTS, COMMON_ERRORS)
+SET LINT_CLEAN := <IS_CLEAN> (from "Agent Inference" using LINT)
+</process>
+
+<process id="load-skill-builder" name="Load Skill Builder">
+SET SKILL_BASE := <BASE_DIR> (from "Agent Inference" using SKILL_PATH)
+SET BUILD_PROCESS_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.build_process)
+READ file at BUILD_PROCESS_PATH
+CAPTURE BUILD_SKILL_CONTENT from read result
+SET GUIDE_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.guide)
+READ file at GUIDE_PATH
+CAPTURE GUIDE_CONTENT from read result
+SET TEMPLATE_PATH := <PATH> (from "Agent Inference" using SKILL_BASE, SKILL_AUTHORING.template)
+TELL "Skill builder loaded. Following build-skill process workflow." level=brief
+</process>
+</processes>
+
+<input>
+USER_INPUT is the user's latest message containing goals or answers.
+</input>
diff --git a/.github/skills/agnostic-prompt-standard/processes/build-skill.md b/.github/skills/agnostic-prompt-standard/processes/build-skill.md
new file mode 100644
index 0000000..d7d4870
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/processes/build-skill.md
@@ -0,0 +1,277 @@
+<instructions>
+You MUST load the target platform adapter from PLATFORMS_REL before generating any output.
+You MUST derive tool names, file paths, and frontmatter format from the loaded adapter.
+You MUST NOT embed platform-specific tool names, paths, or conventions in generated skill content.
+You MUST elicit domain, purpose, and audience before scaffolding any files.
+You MUST determine the source mode before proceeding: from-scratch, from-docs, or from-codebase.
+You MUST load the skill template from TEMPLATE_REL_PATH as the scaffolding seed.
+You MUST load the authoring guide from GUIDE_REL_PATH for reference during generation.
+You MUST load APS references 00-structure, 01-vocabulary, and 02-linting from APS_REFERENCES_REL.
+You MUST generate a valid SKILL.md with complete frontmatter as the first file.
+You MUST create at least one reference document in the skill.
+You SHOULD create constants and formats only when the domain requires structured data or output contracts.
+You MUST validate all generated files against the VALIDATION_CHECKLIST.
+You MUST ask no more than two blocking questions per turn.
+You SHOULD write files directly when the target path has no existing files and scope is unambiguous.
+You MUST present the skill plan for approval when scope is ambiguous or the target directory has existing files.
+You MUST use NAMING_RULES for all generated file and symbol names.
+You MUST use logical tool names that the platform adapter resolves to actual implementations.
+You MUST follow DIRECTORY_STRUCTURE for the generated skill layout.
+You SHOULD generate process files only when the skill encodes executable workflows.
+You MUST report validation results and offer fixes for any issues found.
+</instructions>
+
+<constants>
+TEMPLATE_REL_PATH: "_template/"
+GUIDE_REL_PATH: "guides/skill-authoring-v1.0.0.guide.md"
+APS_REFERENCES_REL: "references/"
+PLATFORMS_REL: "platforms/"
+
+SOURCE_MODES: JSON<<
+{
+  "from-codebase": {
+    "description": "Analyze existing code to extract domain knowledge",
+    "required_inputs": ["codebase_path"],
+    "tools": ["Glob", "Grep", "Read"]
+  },
+  "from-docs": {
+    "description": "Build skill from existing documentation or specifications",
+    "required_inputs": ["doc_paths"],
+    "tools": ["Read"]
+  },
+  "from-scratch": {
+    "description": "Build skill from user-described domain knowledge",
+    "required_inputs": ["domain_description"],
+    "tools": []
+  }
+}
+>>
+
+SKILL_FRONTMATTER_TEMPLATE: TEXT<<
+---
+name: <skill-id>
+description: "<One-sentence skill description>"
+license: MIT
+metadata:
+  author: "<Author Name>"
+  spec_version: "1.0"
+  framework_revision: "1.0.0"
+  last_updated: "<YYYY-MM-DD>"
+---
+>>
+
+NAMING_RULES: TEXT<<
+Skill IDs: kebab-case, unique within installation scope.
+Reference files: NN-<name>.md (zero-padded sequence, kebab-case name).
+Constant symbols: UPPER_SNAKE_CASE matching ^[A-Z0-9_]{2,24}$.
+Format IDs: UPPER_SNAKE_CASE with version suffix (e.g., REPORT_V1).
+Process IDs: kebab-case matching ^[a-z][a-z0-9_-]{1,63}$.
+Process files: <process-name>.md in processes/ directory.
+Asset files: <category>-<descriptor>-v<VERSION>.example.md.
+Guide files: <descriptor>-v<VERSION>.guide.md in guides/ directory.
+>>
+
+VALIDATION_CHECKLIST: TEXT<<
+1. SKILL.md exists with valid YAML frontmatter.
+2. Frontmatter contains name and description fields.
+3. Reference files follow NN-<name>.md naming convention.
+4. No tab characters in any generated file (AG-011).
+5. No comment syntax in APS sections (AG-010).
+6. All format placeholders have WHERE definitions (AG-041).
+7. Placeholder count in body matches WHERE count (AG-042).
+8. Placeholders use <UPPER_SNAKE> format (AG-043).
+9. All where: keys in lexicographic order (AG-012).
+10. Process and tool IDs are backticked (AG-003).
+11. APS sections appear in correct order when present (00-structure).
+>>
+
+DIRECTORY_STRUCTURE: TEXT<<
+<skill-id>/
+  SKILL.md
+  references/
+    00-<name>.md
+  assets/
+    constants/
+    formats/
+  processes/
+  guides/
+  scripts/
+>>
+</constants>
+
+<formats>
+<format id="SKILL_PLAN_V1" name="Skill Plan" purpose="Present the proposed skill structure for approval">
+## Skill Plan: <SKILL_NAME>
+
+**Domain:** <DOMAIN>
+**Purpose:** <PURPOSE>
+**Source mode:** <MODE>
+
+### Proposed files
+<FILE_LIST>
+
+### Directory structure
+<DIR_TREE>
+
+WHERE:
+- <DIR_TREE> is String; ASCII tree showing the proposed directory layout.
+- <DOMAIN> is String; the knowledge domain the skill covers.
+- <FILE_LIST> is Markdown numbered list; each entry has path and one-line description.
+- <MODE> is String; one of from-scratch, from-docs, from-codebase.
+- <PURPOSE> is String; one sentence describing what the skill enables.
+- <SKILL_NAME> is String; human-readable skill name.
+</format>
+
+<format id="SKILL_FILE_V1" name="Skill File Output" purpose="Report on a single generated file">
+### <FILE_PATH>
+**Status:** <VALIDATION_STATUS>
+<ISSUES>
+
+WHERE:
+- <FILE_PATH> is Path; relative path from the skill root.
+- <ISSUES> is String; validation issues found, or empty if none.
+- <VALIDATION_STATUS> is String; one of pass, warn, fail.
+</format>
+
+<format id="SKILL_SUMMARY_V1" name="Skill Build Summary" purpose="Summarize the completed skill build">
+## Skill Build Complete: <SKILL_NAME>
+
+### Files created
+<FILES_CREATED>
+
+### Validation
+**Result:** <OVERALL_STATUS>
+<VALIDATION_DETAILS>
+
+### Next steps
+<NEXT_STEPS>
+
+WHERE:
+- <FILES_CREATED> is Markdown numbered list; paths of all generated files.
+- <NEXT_STEPS> is Markdown bullet list; recommended follow-up actions.
+- <OVERALL_STATUS> is String; one of pass, warn, fail.
+- <SKILL_NAME> is String; human-readable skill name.
+- <VALIDATION_DETAILS> is String; summary of validation results per file.
+</format>
+</formats>
+
+<runtime>
+SOURCE_MODE: ""
+SKILL_ID: ""
+SKILL_DOMAIN: ""
+SKILL_PURPOSE: ""
+PLAN_APPROVED: false
+FILES_GENERATED: 0
+VALIDATION_RESULT: ""
+</runtime>
+
+<triggers>
+<trigger event="user_message" target="build-router" />
+</triggers>
+
+<processes>
+<process id="build-router" name="Build Router">
+TELL "Routing skill build request" level=brief
+IF SOURCE_MODE = "":
+  RUN `init-context`
+  RUN `elicit-domain`
+IF PLAN_APPROVED = false:
+  RUN `plan-skill`
+IF PLAN_APPROVED = true:
+  RUN `generate-skill`
+  RUN `validate-skill`
+</process>
+
+<process id="init-context" name="Initialize Context">
+TELL "Loading authoring context from APS skill" level=brief
+PAR:
+  USE `Read` where: path=GUIDE_REL_PATH
+  USE `Read` where: path=APS_REFERENCES_REL + "00-structure.md"
+  USE `Read` where: path=APS_REFERENCES_REL + "01-vocabulary.md"
+  USE `Read` where: path=APS_REFERENCES_REL + "02-linting-and-formatting.md"
+JOIN:
+  CAPTURE GUIDE from `Read`
+  CAPTURE STRUCTURE_REF from `Read`
+  CAPTURE VOCABULARY_REF from `Read`
+  CAPTURE LINTING_REF from `Read`
+TELL "Loaded authoring guide and APS references" level=brief
+SET PLATFORM_ADAPTER := "" (from "Agent Inference")
+IF PLATFORM_ADAPTER != "":
+  USE `Read` where: path=PLATFORMS_REL + PLATFORM_ADAPTER + "/adaptor.md"
+  CAPTURE ADAPTER from `Read`
+  TELL "Loaded platform adapter" level=brief
+USE `Read` where: path=TEMPLATE_REL_PATH + "SKILL.md"
+CAPTURE TEMPLATE from `Read`
+TELL "Context initialization complete" level=brief
+</process>
+
+<process id="elicit-domain" name="Elicit Domain">
+TELL "Gathering skill requirements" level=brief
+SET SKILL_DOMAIN := "" (from "Agent Inference")
+SET SKILL_PURPOSE := "" (from "Agent Inference")
+SET SKILL_ID := "" (from "Agent Inference")
+SET SOURCE_MODE := "" (from "Agent Inference")
+IF SOURCE_MODE = "from-docs":
+  TELL "Reading source documents" level=brief
+  SET DOC_PATHS := "" (from "Agent Inference")
+  FOREACH DOC IN DOC_PATHS:
+    USE `Read` where: path=DOC
+    CAPTURE DOC_CONTENT from `Read`
+IF SOURCE_MODE = "from-codebase":
+  TELL "Analyzing codebase for domain extraction" level=brief
+  SET CODEBASE_PATH := "" (from "Agent Inference")
+  PAR:
+    USE `Glob` where: path=CODEBASE_PATH, pattern="**/*"
+    USE `Grep` where: path=CODEBASE_PATH, pattern="class|interface|function|def"
+  JOIN:
+    CAPTURE FILE_LIST from `Glob`
+    CAPTURE CODE_PATTERNS from `Grep`
+TELL "Domain elicitation complete" level=brief
+</process>
+
+<process id="plan-skill" name="Plan Skill">
+TELL "Planning skill structure" level=brief
+USE `Read` where: path=TEMPLATE_REL_PATH + "SKILL.md"
+CAPTURE TEMPLATE from `Read`
+SET PLANNED_FILES := "" (from "Agent Inference")
+SET PLANNED_STRUCTURE := "" (from "Agent Inference")
+RETURN: format="SKILL_PLAN_V1", dir_tree=PLANNED_STRUCTURE, domain=SKILL_DOMAIN, file_list=PLANNED_FILES, mode=SOURCE_MODE, purpose=SKILL_PURPOSE, skill_name=SKILL_ID
+SET PLAN_APPROVED := true (from "Agent Inference")
+</process>
+
+<process id="generate-skill" name="Generate Skill">
+TELL "Generating skill files" level=brief
+SET FILE_COUNT := 0 (from "Agent Inference")
+SET CURRENT_FILE := "" (from "Agent Inference")
+FOREACH FILE IN PLANNED_FILES:
+  SET CURRENT_FILE := FILE (from "Agent Inference")
+  SET FILE_CONTENT := "" (from "Agent Inference")
+  USE `Write` where: content=FILE_CONTENT, path=CURRENT_FILE
+  SET FILE_COUNT := FILE_COUNT + 1 (from "Agent Inference")
+  TELL "Generated file" level=detail
+SET FILES_GENERATED := FILE_COUNT (from "Agent Inference")
+TELL "File generation complete" level=brief
+</process>
+
+<process id="validate-skill" name="Validate Skill">
+TELL "Validating generated skill" level=brief
+SET ISSUES := "" (from "Agent Inference")
+SET OVERALL := "pass" (from "Agent Inference")
+FOREACH FILE IN PLANNED_FILES:
+  USE `Read` where: path=FILE
+  CAPTURE CONTENT from `Read`
+  SET FILE_STATUS := "pass" (from "Agent Inference")
+  SET FILE_ISSUES := "" (from "Agent Inference")
+  RETURN: format="SKILL_FILE_V1", file_path=FILE, issues=FILE_ISSUES, validation_status=FILE_STATUS
+  IF FILE_STATUS != "pass":
+    SET OVERALL := FILE_STATUS (from "Agent Inference")
+SET VALIDATION_RESULT := OVERALL (from "Agent Inference")
+RETURN: format="SKILL_SUMMARY_V1", files_created=PLANNED_FILES, next_steps=ISSUES, overall_status=OVERALL, skill_name=SKILL_ID, validation_details=ISSUES
+</process>
+</processes>
+
+<input>
+USER_INPUT is the user message describing the skill to build or providing answers to elicitation questions.
+SKILL_DOMAIN is extracted from USER_INPUT representing the knowledge domain.
+SKILL_PURPOSE is extracted from USER_INPUT representing the intended use.
+</input>
diff --git a/.github/skills/agnostic-prompt-standard/references/00-structure.md b/.github/skills/agnostic-prompt-standard/references/00-structure.md
new file mode 100644
index 0000000..6c98d33
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/00-structure.md
@@ -0,0 +1,174 @@
+# 00 Structure
+
+This document defines the **required top-level prompt envelope** and the structural rules for
+`<triggers>` and `<processes>`.
+
+## Top-level sections
+
+A conforming prompt MUST be composed of the following top-level sections in this exact order:
+
+1. `<instructions>…</instructions>`
+2. `<constants>…</constants>`
+3. `<formats>…</formats>`
+4. `<runtime>…</runtime>`
+5. `<triggers>…</triggers>`
+6. `<processes>…</processes>`
+7. `<input>…</input>`
+
+Normative structural config (informative to engines, but requirements above are authoritative):
+
+```yaml
+prompt_sections:
+  order: [instructions, constants, formats, runtime, triggers, processes, input]
+  tags:
+    - <instructions>…</instructions>
+    - <constants>…</constants>
+    - <formats>…</formats>
+    - <runtime>…</runtime>
+    - <triggers>…</triggers>
+    - <processes>…</processes>
+    - <input>…</input>
+```
+
+### General rules
+
+- Each top-level section MUST appear **at most once**.
+- The `<triggers>` and `<processes>` sections are **executable**.
+- Comments (`//`) are forbidden in all sections (see **02 Linting and formatting**).
+- `<constants>` are **read-only** and MUST be resolved before any tool invocation.
+- `<constants>` take precedence over `<runtime>` if the same symbol is defined in both.
+- Engines SHOULD raise an error or warning when a symbol is defined in both `<constants>` and
+  `<runtime>`, as this indicates a prompt authoring mistake. If both exist, `<constants>` takes
+  precedence.
+
+## `<constants>` section
+
+The `<constants>` block MAY include read-only constant bindings.
+
+Constants MUST use one of the following forms:
+
+1. Inline constant: `SYMBOL: VALUE` where `VALUE` is `String | Number | Boolean | JSON`.
+2. Block constant: `SYMBOL: <BLOCK_TYPE><<` then BODY lines then a closing delimiter line `>>`.
+
+`<BLOCK_TYPE>` MUST be one of: `JSON`, `TEXT`, `YAML`, `CSV`.
+
+Block constant opening lines MUST:
+
+- Use exactly one ASCII space after `:`
+- Contain no spaces before `<<`
+
+Valid openers:
+
+- `SYMBOL: JSON<<`
+- `SYMBOL: TEXT<<`
+- `SYMBOL: YAML<<`
+- `SYMBOL: CSV<<`
+
+Block constant closing delimiter MUST be a line whose content is exactly `>>` starting at column 1
+(no leading/trailing whitespace).
+
+### JSON block constants
+
+- BODY MUST parse as `JsonValue` per **05 Grammar**; invalid JSON → `AG-007`.
+- Any `UpperSym` that appears inside a JSON block constant BODY MUST resolve from `<constants>`
+  before execution; unresolved → `AG-006`.
+- Engines MUST compile JSON block constants to canonical JSON that conforms to `json_spacing` and
+  lexicographic key order (see **02 Linting and formatting**).
+
+### TEXT block constants
+
+- BODY is a literal String; engines MUST preserve BODY verbatim after newline normalization
+  (CRLF→LF).
+- BODY is the exact text between the newline after the opening line and the newline before the
+  closing delimiter line.
+- Leading/trailing whitespace inside BODY is significant.
+
+### YAML block constants
+
+- BODY MUST parse as valid YAML; invalid YAML → `AG-047`.
+- Any `UpperSym` that appears inside a YAML block constant BODY MUST resolve from `<constants>`
+  before execution; unresolved → `AG-006`.
+- Engines MUST compile YAML block constants to canonical YAML with lexicographic key ordering and
+  consistent indentation (see **02 Linting and formatting**).
+
+### CSV block constants
+
+CSV blocks are for compact tabular data.
+
+- BODY MUST parse as CSV (comma-separated values) using the rules below; invalid CSV → `AG-048`.
+- Separator is `,` (comma).
+- Quote character is `"` (double quote).
+- First record is the header row.
+  - Header fields MUST be unquoted.
+  - Header fields MUST match `JsonKey` per **05 Grammar**.
+  - Header fields MUST be unique.
+- Each subsequent record MUST have the same number of fields as the header row (ragged rows are
+  forbidden).
+- Quoted cell values:
+  - MUST follow RFC 4180 quoting (`""` escapes `"`).
+  - Are always treated as `String` (no constant substitution).
+- Unquoted cell values are parsed in this order:
+  1. If the full cell matches `UpperSym`, it denotes a constant symbol reference.
+     - Engines MUST resolve it from `<constants>` before execution; unresolved → `AG-006`.
+     - The referenced constant MUST be a scalar (`String | Number | Boolean | null`) or the engine
+       MUST raise `AG-048`.
+  2. If the cell matches JSON scalars (`Number`, `true`, `false`, `null`), it becomes that JSON
+     scalar.
+  3. Otherwise the cell is a `String` (no trimming).
+- Engines MUST compile CSV block constants to canonical JSON as a `JsonArr` of `JsonObj` rows using
+  header fields as keys (see **02 Linting and formatting**).
+  - Record order MUST be preserved.
+  - Row object keys MUST be emitted in lexicographic order in canonical JSON form.
+
+### Block type selection guidance
+
+Prefer CSV blocks for compact tabular data with a header row and consistent columns.
+
+Prefer YAML blocks for structured data unless JSON has a specific advantage (e.g., the constant
+represents an actual JSON payload or JSON Schema).
+
+Prefer TEXT blocks only when the constant must remain opaque (verbatim).
+
+## `<processes>` section
+
+The `<processes>` block MUST contain one or more `<process>` tags.
+
+### `<process>` tag
+
+Tag syntax:
+
+```text
+<process id="PROCESS_ID" [name="..."] [args="ARG: TYPE, ..."]>
+  …
+</process>
+```
+
+Example:
+
+```text
+<process id="calc_tax" args="amount: Number, region: String">
+  …
+</process>
+```
+
+Rules:
+
+- The content of `<process>` MUST conform to **05 Grammar**.
+- Variables defined via `SET` inside a process are local to that process unless explicitly
+  `RETURN`ed.
+- The engine/LSP MUST raise `AG-044` if a `RUN` statement fails to provide arguments matching the
+  signature.
+
+## `<triggers>` section
+
+Purpose: maps external events to the execution of a specific `process_id`.
+
+Trigger syntax:
+
+```text
+<trigger event="EVENT_TYPE" [pattern="REGEX"] target="PROCESS_ID" />
+```
+
+Validation:
+
+- `target` MUST resolve to a valid `<process id="…">` (`AG-004`).
diff --git a/.github/skills/agnostic-prompt-standard/references/01-vocabulary.md b/.github/skills/agnostic-prompt-standard/references/01-vocabulary.md
new file mode 100644
index 0000000..5a0b000
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/01-vocabulary.md
@@ -0,0 +1,124 @@
+# 01 Vocabulary
+
+This document defines the **normative language** and the authoring vocabulary constraints used
+throughout APS.
+
+## Normative terms
+
+RFC 2119 terms **MUST**, **MUST NOT**, **SHOULD**, **SHOULD NOT**, **MAY** are normative.
+
+## Text types
+
+The following text types are normative and MAY be used to classify prose within a prompt or its
+supporting documentation:
+
+```yaml
+text_types:
+  - Procedure
+  - Description
+  - Safety
+  - Observation
+  - Requirement
+  - Definition
+  - Declaration
+  - Constraint
+  - Conditional
+```
+
+## Tense and voice
+
+```yaml
+tense_voice:
+  allowed_verbs:
+    - infinitive
+    - imperative
+    - simple_present
+    - simple_past
+    - simple_future_will
+  disallowed:
+    - progressive
+    - perfect
+    - going_to_future
+  procedures: active_only
+  descriptions: passive_only_if_agent_unknown
+```
+
+## Dictionary and terminology
+
+- Authors SHOULD use approved words from a Dictionary with approved POS/meaning.
+- Technical terms are allowed if defined on first use and linked by `term_id` and `lexicon_edition`.
+- Multi-word nouns MUST be ≤ 3 words unless explicitly whitelisted.
+
+## Identifiers
+
+In general, specification identifiers SHOULD be short, ASCII, and consistent.
+
+```yaml
+identifiers:
+  # Applies to glossary / lexicon identifiers and similar spec IDs.
+  spec_ids:
+    style: UpperCamel_Segments
+    ascii_only: true
+    no_hyphens: true
+    max_length: 30
+```
+
+> NOTE: Process/tool identifiers, symbols, and placeholders used by the agentic control DSL have
+> their own stricter patterns; see **03 Agentic control**.
+
+## Sentence, paragraph, and list limits
+
+```yaml
+sentence_limits:
+  procedures: 20
+  descriptions: 25
+
+paragraph_limits:
+  sentences_max: 6
+  one_topic: true
+
+lists:
+  steps_numbered: true
+  supportive_bullets: true
+```
+
+## Numbers, units, and time
+
+```yaml
+numbers_units_time:
+  numbers:
+    decimals: "."
+    thousands: "U+2009 (thin space)"
+
+  units:
+    format: "<number><space><unit>"
+    percent: "50 %"
+    temperature: "60 °C"
+    symbols: middle_dot_between_compounds # U+00B7
+    catalog: units.json (project)
+
+  time:
+    iso8601: true
+    default_tz: "Z"
+    local_times_require_offset_or_iana: true
+```
+
+## Safety vocabulary
+
+```yaml
+safety:
+  taxonomy: [WARNING, CAUTION, NOTICE]
+  wrapper: SAF
+  imperative_required: true
+```
+
+## `<instructions>` line discipline
+
+Inside `<instructions>`:
+
+- Instructions MUST use **one directive per line**.
+- Each line MUST be a single imperative or declarative that changes system behavior.
+- Multiple sentences per line are forbidden.
+- Blank lines inside `<instructions>` are forbidden.
+
+The engine/LSP MUST raise `AG-033` when this policy is violated.
diff --git a/.github/skills/agnostic-prompt-standard/references/02-linting-and-formatting.md b/.github/skills/agnostic-prompt-standard/references/02-linting-and-formatting.md
new file mode 100644
index 0000000..56955b1
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/02-linting-and-formatting.md
@@ -0,0 +1,158 @@
+# 02 Linting and formatting
+
+This document defines the **compile-time and lint-time** formatting rules.
+
+## Newlines and XML-like tags
+
+Newline rule (normative):
+
+- There MUST be exactly one newline after an opening XML-like tag.
+- There MUST be exactly one newline before a closing XML-like tag.
+
+This applies to top-level sections (`<instructions>`, `<constants>`, `<formats>`, `<runtime>`,
+`<triggers>`, `<processes>`, `<input>`) and to nested tags like `<format>` and `<process>`.
+
+## Tabs and whitespace
+
+- Tab characters (`\t`) are forbidden anywhere in a prompt. Tabs MUST raise `AG-011`.
+- Engines MUST treat excessive inter-token padding whitespace as a compile error (`AG-031`) when
+  compiled/normalized form requires exactly one ASCII space.
+
+## Comments
+
+Comments (`//`) are forbidden in all sections of a conforming prompt. Any line whose first two
+non-whitespace characters are `//` MUST raise `AG-010`.
+
+## Unicode and quotes
+
+- Prompts MUST be NFC normalized.
+- Strings MUST use ASCII double quotes (`"`) only. Smart quotes are forbidden.
+
+## Canonical JSON spacing
+
+Engines that compile or canonicalize JSON MUST emit **canonical JSON** using the rules below:
+
+- After `:`, exactly one ASCII space.
+- After `,`, exactly one ASCII space.
+- No interior spaces immediately inside `{` `}` `[` `]`.
+  - Empty containers are `{}` and `[]`.
+- Keys in objects MUST be in lexicographic order.
+
+Source form inside JSON block constants MAY contain arbitrary newlines/indentation, but engines
+MUST parse and re-emit canonical JSON at compile time.
+
+## Canonical YAML formatting
+
+Engines that compile or canonicalize YAML MUST emit **canonical YAML** using the rules below:
+
+- Keys in mappings MUST be in lexicographic order.
+- Indentation MUST use exactly two ASCII spaces per nesting level.
+- No trailing whitespace on any line.
+- Strings MUST only be quoted when required by YAML syntax (e.g., values containing `:`, `#`, or
+  leading/trailing whitespace).
+- Empty mappings are `{}` and empty sequences are `[]`.
+
+Source form inside YAML block constants MAY contain arbitrary formatting, but engines MUST parse
+and re-emit canonical YAML at compile time.
+
+## Canonical CSV compilation
+
+Engines that compile CSV block constants MUST:
+
+- Parse CSV per **00 Structure** (header row rules, quoting rules, row width rules).
+- Compile the result to canonical JSON using the rules in **Canonical JSON spacing**.
+- Preserve CSV record order in the compiled JSON array.
+
+If an engine also emits canonical CSV (informative), it SHOULD:
+
+- Use `,` as the separator and `"` as the quote character.
+- Quote a field only when required (contains `,`, `"`, or newline, or has leading/trailing space).
+- Escape `"` as `""` inside quoted fields.
+- Use LF newlines and emit no trailing whitespace.
+
+## `where:` key ordering
+
+In `where:` parameter lists, keys MUST appear in lexicographic order. Violation → `AG-012`.
+
+## Backticked ids
+
+Process and tool ids in statements MUST be wrapped in backticks.
+
+Examples:
+
+- `RUN \`process_id\``
+- `USE \`tool_name\``
+
+Violation → `AG-003` (InvalidId).
+
+## Constants inside JSON values
+
+An `UpperSym` appearing inside JSON objects/arrays denotes a **constant symbol reference**.
+Engines MUST resolve it from `<constants>` before execution or raise `AG-006`.
+
+## Constants inside YAML values
+
+An `UpperSym` appearing inside YAML mappings/sequences/scalars denotes a **constant symbol
+reference**.
+
+Engines MUST resolve it from `<constants>` before execution or raise `AG-006`.
+
+## Constants inside CSV values
+
+In a CSV block constant, an unquoted cell whose full content matches `UpperSym` denotes a
+**constant symbol reference**.
+
+- Engines MUST resolve it from `<constants>` before execution or raise `AG-006`.
+- The referenced constant MUST resolve to a scalar (`String | Number | Boolean | null`) or the
+  engine MUST raise `AG-048`.
+
+## Block constants
+
+Block constants are allowed only inside `<constants>` (see **00 Structure**).
+
+Rules:
+
+- Block constant opening line MUST be `SYMBOL: JSON<<`, `SYMBOL: TEXT<<`, `SYMBOL: YAML<<`, or
+  `SYMBOL: CSV<<` (exactly one ASCII space after `:`).
+- Block constant BODY is line-oriented and terminates at the first line whose content is exactly
+  `>>` starting at column 1.
+- Unknown `<BLOCK_TYPE>` → `AG-046`.
+- Missing closing delimiter `>>` → `AG-045`.
+- Invalid JSON block constant BODY → `AG-007`.
+- Invalid YAML block constant BODY → `AG-047`.
+- Invalid CSV block constant BODY → `AG-048`.
+
+## Format blocks
+
+Rendered format outputs MUST be wrapped in a fenced code block whose info string is exactly
+`format:<ID>` where `<ID>` matches a defined `<format id="...">`.
+
+Rules:
+
+- The fence MUST start at column 1.
+- For any step that requires a format, the agent MUST emit exactly one `format:<ID>` fenced block.
+  Multiple blocks or surrounding prose → `AG-040`.
+
+### WHERE discipline (format contracts)
+
+Every rendered format block MUST include a terminating `WHERE:` section.
+
+Each `<PLACEHOLDER>` token that appears in the body MUST have exactly one definition line in
+`WHERE:`. No extra definitions are allowed.
+
+- Missing/extra/mismatched definitions → `AG-041` / `AG-042`.
+- Placeholders MUST be `<UPPER_SNAKE>`; any other style → `AG-043`.
+
+## RETURN values
+
+`RETURN` supports:
+
+- Symbol lists
+- `key=value` pairs
+- Artifact references of the form:
+
+```json
+{"$artifact":"SYMBOL","hash":"sha256:..."}
+```
+
+See **03 Agentic control** and **05 Grammar** for executable syntax.
diff --git a/.github/skills/agnostic-prompt-standard/references/03-agentic-control.md b/.github/skills/agnostic-prompt-standard/references/03-agentic-control.md
new file mode 100644
index 0000000..9339637
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/03-agentic-control.md
@@ -0,0 +1,233 @@
+# 03 Agentic control
+
+This document defines the **agentic control DSL** used inside `<process>` bodies.
+
+## Keywords
+
+```yaml
+keywords:
+  control: [GIVEN, WHEN, THEN, IF, ELSE IF, ELSE, IN]
+  actions: [RUN, USE, CAPTURE, SET, UNSET, RETURN, ASSERT]
+  story: [TELL, SNAP, MILESTONE]
+  blocks: [WITH, PAR, JOIN, TRY, FOREACH, RECOVER]
+  modifiers: [atomic, timeout_ms, retry]
+```
+
+## Identifiers and reserved tokens
+
+```yaml
+identifiers:
+  symbol:
+    regex: "^[A-Z0-9_]{2,24}$"
+    unique: true
+
+  process_id:
+    regex: "^[a-z][a-z0-9_-]{1,63}$"
+    unique: true
+
+  tool_name:
+    regex: "^[a-z][a-z0-9_-]{1,63}$"
+    registered_by_engine: true
+
+  placeholder:
+    syntax: "<UPPER_SNAKE>"
+    charset: "A-Z0-9_"
+    resolvable: true
+
+  reserved:
+    - GIVEN
+    - WHEN
+    - THEN
+    - IF
+    - ELSE
+    - FOREACH
+    - IN
+    - TRY
+    - RECOVER
+    - RUN
+    - USE
+    - SET
+    - CAPTURE
+    - RETURN
+    - ASSERT
+    - SHOULD
+    - MAY
+    - AND
+    - OR
+    - NOT
+    - WITH
+    - PAR
+    - JOIN
+    - TELL
+    - SNAP
+    - MILESTONE
+```
+
+Reserved words cannot be used as ids/keys/symbols (`AG-002`).
+
+## GIVEN / WHEN / THEN (BDD pattern)
+
+These keywords support Behavior-Driven Design (BDD) style specifications:
+
+- `GIVEN`: establishes preconditions or context that must hold before execution.
+- `WHEN`: describes a trigger, event, or condition that initiates action.
+- `THEN`: specifies expected outcomes or postconditions after execution.
+
+Each keyword opens a block with `:` (Python-style). The block body contains statements that execute
+when the condition is satisfied. Engines SHOULD evaluate conditions in lexical order.
+
+## Strings, booleans, and numbers
+
+```yaml
+strings_booleans_numbers:
+  strings:
+    quote: double_only
+  booleans: [true, false]
+  numbers:
+    grammar: JSON_number
+    thousands: forbidden
+```
+
+## Determinism
+
+- External `USE` invocations SHOULD be idempotent; engines MAY deduplicate based on a stable hash
+  of inputs.
+- `CAPTURE` is the binding point; `USE` does not mutate the symbol table by itself.
+
+## Storytelling
+
+These statements produce narrative/logging events and are not allowed to change program state
+except as explicitly defined by the engine:
+
+- `TELL`: emits a narrative event (what/why/outcome/level).
+- `SNAP`: snapshots selected symbols; supports delta and redact lists.
+- `MILESTONE`: semantic checkpoint message (sugar for `TELL` with `type="milestone"`).
+
+## WITH block
+
+- `WITH {defaults}:` applies key/value defaults (e.g., `endpoint=...`) to enclosed `RUN`/`USE`/
+  `CAPTURE` until the block end.
+- Nested `WITH` blocks shadow outer defaults; scope does not leak across the closing boundary.
+
+## PAR / JOIN concurrency
+
+`PAR` and `JOIN` define deterministic concurrency:
+
+- `PAR:` launches one-or-more `USE` statements concurrently in **lexical order**; each child gets
+  index `[0..n-1]`.
+- `JOIN:` is the first legal point to `CAPTURE` results of prior PAR tools.
+- `CAPTURE` order MUST follow the **lexical order** of the corresponding `USE` statements,
+  regardless of completion time.
+- If any child fails hard, `JOIN` raises a composite error including the first hard error and
+  aggregates others as `suppressed`.
+
+Engines SHOULD log deterministic span indices and MUST NOT perform speculative execution.
+
+## FOREACH iteration
+
+`FOREACH` provides deterministic iteration over symbol arrays:
+
+- `FOREACH item IN ITEMS:` iterates over each element in the `ITEMS` array in **index order**.
+- The loop variable (`item`) is bound to the current element for each iteration.
+- Loop body statements execute sequentially; the engine MUST NOT parallelize unless explicitly
+  wrapped in `PAR`.
+- If `ITEMS` is empty, the loop body is skipped entirely.
+- The loop variable is scoped to the block; it is undefined after the closing boundary.
+
+Engines SHOULD expose the current index via a deterministic mechanism (e.g., `_INDEX` symbol).
+
+## TRY / RECOVER error handling
+
+`TRY` and `RECOVER` define structured error handling:
+
+- `TRY:` begins a guarded block; statements execute until completion or first hard error.
+- `RECOVER (err):` binds the error to the named variable (`err`) and executes recovery statements.
+- If no error occurs, the `RECOVER` block is skipped.
+- Recovery statements MAY access the error variable to inspect type, message, or context.
+- Nested `TRY` blocks are permitted; inner handlers take precedence.
+
+Error binding follows engine-defined schema; at minimum, engines MUST expose `err.type` and
+`err.message`.
+
+## Invocation syntax (normative)
+
+The following describes statement syntax at a human-readable level. The authoritative grammar is
+in **05 Grammar**.
+
+```text
+RUN `process_id` [where: k1=V1, ...]
+
+USE `tool_name` [where: k1=V1, ...] [(atomic[, timeout_ms=NUM][, retry=NUM])]
+
+CAPTURE S1[, S2 ...] from `tool_name` [map: "path1"→S1, "path2?"→S2 ...]
+  - Optional field via suffix '?'; no error if missing; symbol unchanged.
+
+SET SYMBOL := VALUE [(from SOURCE)]
+  - SOURCE ∈ { `tool`, INP, UpperSym, "Agent Inference" }
+
+UNSET SYMBOL
+
+RETURN: SYMBOL[, SYMBOL...]
+RETURN: key=VALUE[, key=VALUE ...]
+  - VALUE may be an artifact reference: {"$artifact":"SYMBOL","hash":"sha256:..."}.
+
+ASSERT <condition>
+ASSERT ALL: [ <condition>, <condition>, ... ]
+
+TELL "message" [why:SYMBOL] [level={brief|full}] [outcome:"text"]
+MILESTONE "title"
+
+SNAP [SYM1, SYM2 ...] [delta=true|false] [redact=[SYM_A, SYM_B ...]]
+```
+
+## Arguments and values
+
+```yaml
+arguments:
+  allowed_values:
+    - String
+    - Number
+    - Boolean
+    - JSON
+    - UpperSym
+    - <PLACEHOLDER>
+    - enum(V1,V2,...)
+
+  choice_sets: "{V1|V2|...} allowed in spec text where indicated; engine turns into enum() at compile time."
+  const_refs: "UpperSym MAY appear inside JSON objects/arrays and are resolved from <constants>."
+  enums: "enum(A,B,...) becomes a choice set for validation."
+```
+
+## Placeholder resolution
+
+```yaml
+placeholder_resolution:
+  order: [INP, CONSTANTS, RUNTIME, Agent Inference (only if allowed)]
+  allow_agent_inference_placeholders: false
+```
+
+Rules:
+
+- Unresolved placeholder → `AG-006`.
+- If inference occurs under a non-strict policy, the engine MUST emit `AG-W03` with the inferred
+  value and a deterministic input hash in the invocation log.
+
+## Naming policy
+
+- IDs/keys MUST be lowercase.
+- Symbols MUST be `UPPER_SNAKE`.
+- Reserved words cannot be used as IDs/keys/symbols (`AG-002`).
+
+## Safety policy
+
+```yaml
+safety_policy:
+  defaults: { THR: 0.90, HARM_THR: 0.40 }
+  predicate: HARM := (HSC ≥ HARM_THR) OR (STY_JSON.policy_violation = true)
+  decision:
+    IF TS ≥ THR AND HARM=false: REC := "PROCEED"
+    ELSE IF NPR != "": REC := "PROCEED_WITH_CAUTION"
+    ELSE: REC := "HOLD_FOR_REVIEW"
+  log_thresholds: true
+  randomness: forbidden unless seed provided; otherwise AG-022 (RandomnessPolicy) if policy enabled.
+```
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/references/04-schemas-and-types.md b/.github/skills/agnostic-prompt-standard/references/04-schemas-and-types.md
new file mode 100644
index 0000000..a1a98d1
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/04-schemas-and-types.md
@@ -0,0 +1,135 @@
+# 04 Schemas and types
+
+This document defines the **schemas** and reusable **type contracts** used by APS.
+
+## Formats registry
+
+The `<formats>` section centralizes all human-readable output contracts that a prompt may ask the
+agent to render. This ensures outputs are verifiable, stable, and machine-checkable.
+
+### Requirements
+
+- All format contracts used anywhere in `<instructions>`, `<triggers>`, or `<processes>` MUST be
+  declared inside a single `<formats>` section using one-or-more `<format>` tags.
+- Each `<format>` MUST have a globally unique `id` within the prompt; `name` and `purpose`
+  attributes are RECOMMENDED.
+- The body of each `<format>` MUST describe the contract unambiguously (headers, columns,
+  wrappers, markers, row grammar, allowed values).
+- Rendered output MUST be a single fenced block starting with the exact fence label:
+
+  ```
+  ```format:<FORMAT_ID>
+  ```
+
+  (No spaces around the colon.)
+
+- No explanatory prose MAY appear outside the fenced block for a step that demands a format.
+- If a step references a format id that is not present in `<formats>` → `AG-039`.
+- If the rendered block does not satisfy the contract → `AG-036`.
+- If the block is not wrapped with the required ```format:<ID> fence → `AG-040`.
+
+### Structure
+
+Tag syntax:
+
+```text
+<format id="ID" [name="..."...] [purpose="..."]>
+  …
+</format>
+```
+
+Newline rules apply to `<formats>` and each `<format>` (see **02 Linting and formatting**).
+
+### Placeholders and WHERE
+
+Placeholders and WHERE sections are normative (see also **02 Linting and formatting**):
+
+- Placeholders that appear in the contract body MUST be written as `<UPPER_SNAKE>` using ASCII and
+  `UPPER_SNAKE` case.
+- Every `<format>` body MUST end with a `WHERE:` section that defines each placeholder exactly
+  once.
+- Each WHERE definition line MUST begin with `- <PLACEHOLDER> …` and normatively constrain the
+  placeholder (e.g., “is …”, “∈ { … }”, “matches …”, “example: …”).
+- No placeholder may appear in the body if it is not defined in WHERE → `AG-042`.
+- No placeholder may be defined in WHERE if it does not appear in the body → `AG-042`.
+- Any non-`<…>` placeholder notation (e.g., `{placeholder}`, `$PLACEHOLDER`) is forbidden →
+  `AG-043`.
+- The literal keyword `WHERE:` MUST be uppercase and followed by a newline; inline WHERE text is
+  forbidden → `AG-041`.
+
+### Expression guidance inside WHERE (RECOMMENDED)
+
+- Type: `is <type>` where `<type>` ∈ { String, Integer, Number, Boolean, ISO8601, Markdown, URI,
+  Path }.
+- Choice: `∈ { V1, V2, … }` or `is one of: V1, V2, …`.
+- Shape: `format: "## <TITLE> …"`, `table columns: | A | B | … |`, `regex: ^…$`.
+- Cardinality: `is non-empty`, `is ≤ N chars`, `is comma-separated list of UpperSym`.
+
+### References and phrasing
+
+Prompts SHOULD phrase requirements in `<instructions>` like:
+
+> You MUST conform human-readable outputs to `<formats>` by rendering a single fenced block
+> ```format:<ID>```.
+
+### Enforcement
+
+- WHERE presence/quality and placeholder discipline are enforced at lint time.
+- Violations map to `AG-041` / `AG-042` / `AG-043` or `AG-036` as applicable.
+
+## Result process pattern
+
+Intent: provide a standard **results** process that summarizes execution across processes in a
+pre-defined table for deterministic post-hoc analysis and artifact linking.
+
+Prompts that adopt this pattern MUST:
+
+1. Define `TABLE_PROCESS_RESULTS_V1` inside `<formats>`.
+2. Include a terminal process (RECOMMENDED id: `results` or short `res`) that emits exactly one
+   fenced block ```format:TABLE_PROCESS_RESULTS_V1``` summarizing all processes in lexical order.
+3. Record, at minimum: ProcessId, Name, Status, StartedAt, EndedAt, DurationMs, Outcome,
+   Artifacts, Errors.
+
+Status values MUST be one of: PENDING, RUNNING, OK, WARN, ERROR.
+
+Timestamps MUST be ISO 8601 with "Z" or explicit offset.
+
+Artifacts MUST list symbol names (comma-separated) that were RETURNed or CAPTUREd as outputs.
+
+## Supporting files (external)
+
+These files are **external** and MUST NOT appear in the prompt:
+
+- `config.json`: ALIAS only (see schema).
+- `predefinedTools.json`: tool signatures for lint/IDE help (replaces schema.json).
+- `units.json`: unit catalog used by STE layer.
+
+Policies:
+
+- If a host provides tools/config via higher-level system instructions, the engine MUST ignore any
+  duplicate local definitions to avoid prompt bloat.
+- Embedding `<config>` or `<import>` tags in a prompt is a hard error (`AG-035`).
+
+Style guidelines:
+
+- For `predefinedTools.json`, prefer one tool object per line to improve diffs/merges (best
+  practice; not enforced).
+- Engines that emit `predefinedTools.json` SHOULD preserve or adopt the one-line-per-tool layout;
+  engines MUST accept any valid JSON layout.
+
+## Example format contracts
+
+- Minimal error contract: [../assets/formats/format-error-v1.0.0.example.md](../assets/formats/format-error-v1.0.0.example.md)
+- API coverage table: [../assets/formats/format-table-api-coverage-v1.0.0.example.md](../assets/formats/format-table-api-coverage-v1.0.0.example.md)
+- Code map: [../assets/formats/format-code-map-v1.0.0.example.md](../assets/formats/format-code-map-v1.0.0.example.md)
+- Ideation list: [../assets/formats/format-ideation-list-v1.0.0.example.md](../assets/formats/format-ideation-list-v1.0.0.example.md)
+- Hierarchical outline: [../assets/formats/format-hierarchical-outline-v1.0.0.example.md](../assets/formats/format-hierarchical-outline-v1.0.0.example.md)
+- Markdown table: [../assets/formats/format-markdown-table-v1.0.0.example.md](../assets/formats/format-markdown-table-v1.0.0.example.md)
+- Code changes full: [../assets/formats/format-code-changes-full-v1.0.0.example.md](../assets/formats/format-code-changes-full-v1.0.0.example.md)
+- SMEAC plan: [../assets/formats/format-smeac-plan-v1.0.0.example.md](../assets/formats/format-smeac-plan-v1.0.0.example.md)
+
+## Example constants
+
+- JSON block constant example: [../assets/constants/constants-json-block-v1.0.0.example.md](../assets/constants/constants-json-block-v1.0.0.example.md)
+- TEXT block constant example: [../assets/constants/constants-text-block-v1.0.0.example.md](../assets/constants/constants-text-block-v1.0.0.example.md)
+- CSV block constant example: [../assets/constants/constants-csv-block-v1.0.0.example.md](../assets/constants/constants-csv-block-v1.0.0.example.md)
diff --git a/.github/skills/agnostic-prompt-standard/references/05-grammar.md b/.github/skills/agnostic-prompt-standard/references/05-grammar.md
new file mode 100644
index 0000000..9045599
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/05-grammar.md
@@ -0,0 +1,101 @@
+# 05 Grammar
+
+This document defines the normative EBNF for the agentic control DSL.
+
+> NOTE: This is a reference grammar. Engines MAY extend it, but prompts that claim APS v1.0
+> conformance MUST remain within this grammar unless the host explicitly opts into extensions.
+
+## EBNF
+
+```ebnf
+Letter        = "A"…"Z" | "a"…"z" ;
+LowerLetter   = "a"…"z" ;
+Digit         = "0"…"9" ;
+Space         = " " ;
+Newline       = "\n" ;
+Tab           = "\t" ;
+
+UpperSym      = ( "A"…"Z" | "0"…"9" | "_" ){2,24} ;
+Placeholder   = "<", ( "A"…"Z" | "0"…"9" | "_" ){1,64}, ">" ;
+Bool          = "true" | "false" ;
+Number        = "-"? Digit, { Digit }, [ ".", Digit, { Digit } ] ;
+String        = "\"", { <any char except " or \"> | "\\\"" | "\\\\" }, "\"" ;
+EnumLit       = "enum(", UpperSym, { ",", UpperSym }, ")" ;
+
+BlockType     = "JSON" | "TEXT" | "YAML" | "CSV" ;
+BlockOpen     = UpperSym, ":", Space, BlockType, "<<", EOL ;
+BlockClose    = ">>" ;
+BlockValue    = BlockType, "<<", EOL, { <any line except BlockClose>, EOL }, BlockClose ;
+
+JsonKey       = LowerLetter, { LowerLetter | Digit | "_" | "-" } ;
+JsonValue     = String | Number | Bool | "null" | JsonObj | JsonArr | UpperSym ;
+JsonPair      = "\"", JsonKey, "\"", ":", Space?, JsonValue ;
+JsonObj       = "{", Space?, [ JsonPair, { ",", Space?, JsonPair } ], Space?, "}" ;
+JsonArr       = "[", Space?, [ JsonValue, { ",", Space?, JsonValue } ], Space?, "]" ;
+
+IdLower       = LowerLetter, { LowerLetter | Digit | "_" | "-" } ;
+Key           = IdLower ;
+Value         = String | Number | Bool | JsonObj | JsonArr | UpperSym | Placeholder | EnumLit ;
+
+StaticConst   = UpperSym, ":", Space, ( Value | BlockValue ) ;
+
+Param         = Key, "=", Value ;
+ParamList     = Param, { ",", Space, Param } ;
+
+BacktickId    = "`", IdLower, "`" ;
+
+RunStmt       = "RUN", Space, BacktickId, [ Space, "where:", Space, ParamList ] ;
+UseStmt       = "USE", Space, BacktickId, [ Space, "where:", Space, ParamList ],
+                [ Space, "(", "atomic", [ ",", Space, "timeout_ms", "=", Number ], [ ",", Space, "retry", "=", Number ], ")" ] ;
+CaptureStmt   = "CAPTURE", Space, UpperSym, { ",", Space, UpperSym }, Space, "from", Space, BacktickId,
+                [ Space, "map:", Space, "\"", <path>, "\"", "→", UpperSym, { ",", Space, "\"", <path>, "\"", "→", UpperSym } ] ;
+SetStmt       = "SET", Space, UpperSym, Space, ":=", Space, Value, [ Space, "(", "from ", ( BacktickId | "INP" | UpperSym | "Agent Inference" ), ")" ] ;
+UnsetStmt     = "UNSET", Space, UpperSym ;
+ReturnPairs   = IdLower, "=", Value, { ",", Space, IdLower, "=", Value } ;
+ReturnList    = UpperSym, { ",", Space, UpperSym } ;
+ReturnStmt    = "RETURN", ":", Space, ( ReturnList | ReturnPairs ) ;
+AssertStmt    = "ASSERT", Space, <expr> | "ASSERT ALL:", Space, "[", <expr>, { ",", Space, <expr> }, "]" ;
+TellStmt      = "TELL", [ Space, String ], [ Space, "why:", UpperSym ], [ Space, "level=", ("brief" | "full") ], [ Space, "outcome:", String ] ;
+MileStmt      = "MILESTONE", Space, String ;
+
+SnapList      = "[", UpperSym, { ",", Space, UpperSym }, "]" ;
+RedactList    = "[", UpperSym, { ",", Space, UpperSym }, "]" ;
+SnapStmt      = "SNAP", Space, SnapList, [ Space, "delta", "=", Bool ], [ Space, "redact", "=", RedactList ] ;
+
+IfStmt        = "IF", Space, <expr>, ":" ;
+ElseIfStmt    = "ELSE IF", Space, <expr>, ":" ;
+ElseStmt      = "ELSE", ":" ;
+WhenStmt      = "WHEN", Space, <condition-text-no-colon>, ":" ;
+ThenStmt      = "THEN", Space, <condition-text-no-colon>, ":" ;
+GivenStmt     = "GIVEN", Space, <condition-text-no-colon>, ":" ;
+
+EOL           = Newline ;
+WithBlock     = "WITH", Space, JsonObj, ":", EOL, { <indented Statement>, EOL } ;
+ParBlock      = "PAR", ":", EOL, { <indented UseStmt>, EOL } ;
+JoinBlock     = "JOIN", ":", EOL, { <indented CaptureStmt>, EOL } ;
+
+ForEachStmt   = "FOREACH", Space, IdLower, Space, "IN", Space, UpperSym, ":", EOL, { <indented Statement>, EOL } ;
+
+TryBlock      = "TRY", ":", EOL, { <indented Statement>, EOL },
+                "RECOVER", Space, "(", IdLower, ")", ":", EOL, { <indented Statement>, EOL } ;
+
+WhereSection  = "WHERE:", EOL, { WhereDef, EOL } ;
+WhereDef      = "- ", Placeholder, Space, Constraint ;
+Constraint    = TypeConst | EnumConst | FormatConst | RegexConst ;
+
+TypeConst     = "is", Space, ("String" | "Number" | "Boolean" | "ISO8601" | "URI" | "Path") ;
+EnumConst     = "is one of:", Space, Value, { ",", Space, Value } ;
+FormatConst   = "matches format:", Space, UpperSym ;  # Recursive validation
+RegexConst    = "matches", Space, String ;
+
+Statement     = RunStmt | UseStmt | CaptureStmt | SetStmt | UnsetStmt | ReturnStmt | AssertStmt
+              | TellStmt | MileStmt | WithBlock | ParBlock | JoinBlock | ForEachStmt | TryBlock
+              | IfStmt | ElseIfStmt | ElseStmt | GivenStmt | WhenStmt | ThenStmt | SnapStmt ;
+
+Program       = { Statement, EOL } ;
+```
+
+## Notes (non-normative)
+
+- Indentation is significant for block bodies (`WITH`, `PAR`, `JOIN`, `TRY`, `FOREACH`).
+- `<expr>` and `<path>` are intentionally unspecified in v1.0 and are engine-defined.
diff --git a/.github/skills/agnostic-prompt-standard/references/06-logging-and-privacy.md b/.github/skills/agnostic-prompt-standard/references/06-logging-and-privacy.md
new file mode 100644
index 0000000..763bae2
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/06-logging-and-privacy.md
@@ -0,0 +1,32 @@
+# 06 Logging and privacy
+
+This document defines the normative logging and redaction requirements for APS executors.
+
+## Logging
+
+```yaml
+logging:
+  capture_points: [RUN, USE, CAPTURE, SET, UNSET, ASSERT, RETURN, PAR, JOIN, TELL, SNAP]
+  include:
+    - timestamp
+    - process_id
+    - step_index
+    - action
+    - inputs
+    - outputs
+    - artifacts
+    - prior_hash
+    - new_hash
+    - origin
+    - policy_hash
+```
+
+## Redaction
+
+Engines MUST enforce:
+
+- Secrets/PII MUST be redacted as `[REDACTED]` (`AG-032`).
+- For `SNAP` with `redact=[SYMS]`, engines MUST zeroize the listed symbols in `prior_state`,
+  `new_state`, and `artifacts`.
+- If `TELL` uses `why:SYMBOL` and `SYMBOL` is redacted, only the symbol name may appear; its
+  content MUST NOT.
\ No newline at end of file
diff --git a/.github/skills/agnostic-prompt-standard/references/07-error-taxonomy.md b/.github/skills/agnostic-prompt-standard/references/07-error-taxonomy.md
new file mode 100644
index 0000000..a36a7b3
--- /dev/null
+++ b/.github/skills/agnostic-prompt-standard/references/07-error-taxonomy.md
@@ -0,0 +1,64 @@
+# 07 Error taxonomy
+
+This document defines the normative error and warning codes.
+
+## Errors
+
+```yaml
+errors:
+  hard:
+    - { code: AG-001, name: UndefinedSymbol, desc: Symbol not defined in <constants> or <runtime>. }
+    - { code: AG-002, name: ReservedTokenMisuse, desc: Reserved word used as ID/Key/Symbol. }
+    - { code: AG-003, name: InvalidId, desc: Process/tool/key not matching naming regex. }
+    - { code: AG-004, name: ProcessIdMismatch, desc: RUN references missing <process id="…">. }
+    - { code: AG-006, name: UnresolvedPlaceholder, desc: Placeholder could not be resolved. }
+    - { code: AG-007, name: BadJSON, desc: Invalid JSON value or pair. }
+    - { code: AG-008, name: CaptureMissing, desc: CAPTURE references unknown/never-executed tool. }
+    - { code: AG-009, name: TagMismatch, desc: Unbalanced or wrong closing tag. }
+    - { code: AG-010, name: CommentDetected, desc: Comment present in any section. }
+    - { code: AG-011, name: TabDetected, desc: Tab characters present. }
+    - { code: AG-012, name: KeyOrder, desc: Keys in where: not lexicographic. }
+    - { code: AG-013, name: DuplicateSymbol, desc: Symbol redefined with incompatible type/origin. }
+    - { code: AG-014, name: TimeFormat, desc: Non-ISO 8601 time/offset where required. }
+    - { code: AG-015, name: CasePolicy, desc: Non-lowercase booleans or non-double-quoted strings. }
+    - { code: AG-016, name: ProcessNameAttrMismatch, desc: <process> Name attr missing/malformed. }
+    - { code: AG-017, name: ToolPolicy, desc: Tools used in <triggers>. }
+    - { code: AG-018, name: ConcurrencyPolicy, desc: PAR/JOIN misuse or nondeterministic ordering. }
+    - { code: AG-019, name: ForbiddenSymbolOrigin, desc: SET origin missing/invalid. }
+    - { code: AG-021, name: STEValidationFailed, desc: ste=true text failed STE lints. }
+    - { code: AG-022, name: RandomnessPolicy, desc: Randomness used without seed where policy forbids. }
+    - { code: AG-023, name: WithScopeError, desc: WITH defaults malformed or leaked across scope boundary. }
+    - { code: AG-024, name: AliasMapError, desc: ALIAS mapping invalid or collides with symbol names. }
+    - { code: AG-027, name: TimeoutRetryPolicy, desc: timeout_ms/retry invalid type/range. }
+    - { code: AG-028, name: CapturePathError, desc: CAPTURE map path invalid or type coercion failed. }
+    - { code: AG-029, name: AssertInvalid, desc: ASSERT expression invalid or unsafely side-effecting. }
+    - { code: AG-030, name: SemicolonDetected, desc: Semicolon ';' used where newline termination is required. }
+    - { code: AG-031, name: PaddingWhitespace, desc: Excess inter-token spaces detected; exactly one ASCII space required in compiled form. }
+    - { code: AG-032, name: SensitiveInLog, desc: Secrets/PII leaked in logs or errors. }
+    - { code: AG-033, name: InstructionsLinePolicy, desc: Multiple sentences per line, blank lines, or non-directive lines present in <instructions>. }
+    - { code: AG-034, name: PredefinedToolCollision, desc: Conflicting tool signatures across host and predefinedTools.json. }
+    - { code: AG-035, name: InPromptConfigOrImports, desc: Presence of <config> or <import> tags in prompt. }
+    - { code: AG-036, name: FormatContractViolation, desc: Output does not match the referenced <format id="…"> template (missing headers/columns/markers/placeholders not resolved). }
+    - { code: AG-037, name: DictReferenceForbidden, desc: DICT-style reference @"…" used; constants must be defined in <constants>. }
+    - { code: AG-038, name: DictInConfigForbidden, desc: config.json contains a DICT key; migrate constants to <constants>. }
+    - { code: AG-039, name: FormatUndefined, desc: A step references a format id that is not defined in <formats>. }
+    - { code: AG-040, name: FormatFenceError, desc: Missing or malformed ```format:<ID> fenced block; multiple format blocks or surrounding prose where a single block is required. }
+    - { code: AG-041, name: FormatWhereMissing, desc: WHERE: section missing or not uppercase when placeholders are present (or required by policy). }
+    - { code: AG-042, name: PlaceholderMismatch, desc: Placeholder appears in body but not in WHERE, or defined in WHERE but not present in body. }
+    - { code: AG-043, name: PlaceholderStyleError, desc: Placeholder not in <UPPER_SNAKE> form or not wrapped in angle brackets. }
+    - { code: AG-044, name: ProcessArgsMismatch, desc: RUN statement arguments do not match the target process signature (missing, extra, or type-incompatible arguments). }
+    - { code: AG-045, name: BlockConstantUnterminated, desc: Block constant missing closing delimiter line >>. }
+    - { code: AG-046, name: BlockConstantTypeUnknown, desc: Block constant uses unknown <BLOCK_TYPE>; expected JSON, TEXT, YAML, or CSV. }
+    - { code: AG-047, name: BadYAML, desc: Invalid YAML block constant body. }
+    - { code: AG-048, name: BadCSV, desc: Invalid CSV block constant body (parse failure, invalid header, ragged rows, or invalid cell). }
+
+  warnings:
+    - { code: AG-W01, name: SymbolNotUsed, desc: Defined but never used. }
+    - { code: AG-W02, name: LaxTime, desc: Step without explicit time where policy requires. }
+    - { code: AG-W03, name: HeuristicInference, desc: Placeholder resolved by Agent Inference under strict policy. }
+```
+
+## Required behaviors
+
+- Engines MUST treat all `errors.hard` codes as fatal for the current compile/run.
+- Engines MAY continue on `warnings`, but MUST surface them to the caller.
diff --git a/.github/skills/agnostic-prompt-standard/scripts/.gitkeep b/.github/skills/agnostic-prompt-standard/scripts/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/README.md b/README.md
index e099ffd..0ed7c66 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,7 @@
 # Juan's Devcontainer Features:
 
+[![APS version](https://img.shields.io/github/v/release/chris-buckley/agnostic-prompt-standard?label=APS&logo=github)](https://github.com/chris-buckley/agnostic-prompt-standard/releases/tag/v1.1.16)
+
 set of features I use and I think should be included in the registry.
 
 ## Features