@gillcash/necktie 0.2.0

package/.opencode/command/necktie-critique.md

@@ -0,0 +1,5 @@
+---
+description: Challenge an inquiry and surface material blind spots
+---
+
+Use $necktie-critique on: $ARGUMENTS. Test goal alignment, assumptions, evidence needs, and the strongest unasked expert question.

package/.opencode/command/necktie-reverse.md

@@ -0,0 +1,5 @@
+---
+description: Compile iterative context into one executable brief
+---
+
+Use $necktie-reverse on: $ARGUMENTS. Produce a self-contained brief that can be executed in a fresh session from raw evidence.

package/.opencode/command/necktie-review.md

@@ -0,0 +1,5 @@
+---
+description: Independently gate a candidate deliverable
+---
+
+Use $necktie-review on: $ARGUMENTS. Judge the exact candidate against its brief, evidence, criteria, and verification; return APPROVE, REVISE, or BLOCK.

package/.opencode/command/necktie.md

@@ -0,0 +1,5 @@
+---
+description: Run the explicit, bounded Necktie Loop
+---
+
+Use $necktie for this goal: $ARGUMENTS. Frame, baseline, critique, reverse, execute, review, and verify. Return the final deliverable, reusable execution brief, verification record, material overlooked consideration, and strongest unasked question.

package/.opencode/plugins/necktie-frontmatter.cjs

@@ -0,0 +1,12 @@
+"use strict";
+
+function parseCommandFile(filePath) {
+  const fs = require("node:fs");
+  const content = fs.readFileSync(filePath, "utf8");
+  const match = content.match(/^---\r?\n([\s\S]*?)\r?\n---\r?\n([\s\S]*)$/);
+  if (!match) return null;
+  const description = match[1].match(/description:\s*(.+)/)?.[1]?.trim();
+  return { description, template: match[2].trim() };
+}
+
+module.exports = { parseCommandFile };

package/.opencode/plugins/necktie.mjs

@@ -0,0 +1,35 @@
+import fs from "node:fs";
+import path from "node:path";
+import { createRequire } from "node:module";
+import { fileURLToPath } from "node:url";
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const require = createRequire(import.meta.url);
+const { parseCommandFile } = require("./necktie-frontmatter.cjs");
+const root = path.resolve(__dirname, "../..");
+const skillsDir = path.join(root, "skills");
+
+function coreContext() {
+  return fs.readFileSync(path.join(root, "core", "necktie-core.md"), "utf8").trim();
+}
+
+export default async function necktiePlugin() {
+  return {
+    config: async (config) => {
+      config.command ||= {};
+      const commandDir = path.join(__dirname, "..", "command");
+      for (const file of fs.readdirSync(commandDir).filter((name) => name.endsWith(".md"))) {
+        const parsed = parseCommandFile(path.join(commandDir, file));
+        if (parsed) config.command[path.basename(file, ".md")] = parsed;
+      }
+      config.skills ||= {};
+      config.skills.paths ||= [];
+      if (!config.skills.paths.includes(skillsDir)) config.skills.paths.push(skillsDir);
+    },
+    "experimental.chat.system.transform": async (_input, output) => {
+      const context = coreContext();
+      if (output.system.length) output.system[output.system.length - 1] += `\n\n${context}`;
+      else output.system.push(context);
+    },
+  };
+}

package/.qoder/rules/necktie.md

@@ -0,0 +1,18 @@
+# Necktie Core
+
+Necktie is active for every response.
+
+Before acting, align the requested output with the user's real goal, intended reader, acceptance criteria, constraints, available evidence, and authority. Make the smallest intervention that fully satisfies those conditions. Reuse trusted sources and native capabilities before adding new machinery.
+
+Before the final response:
+
+1. Check the work in proportion to its risk. Correct material errors that you can resolve.
+2. Identify any material consideration the user may have overlooked relative to the goal.
+3. Identify the strongest unasked question that a genuine subject-matter expert would ask, but include it only when its answer could change the decision, result, or risk.
+4. Ask the user a question only when the answer would materially change the objective, evidence, authority, or deliverable. Otherwise state the necessary assumption and proceed.
+
+Never trade away security, privacy, accessibility, input validation at trust boundaries, error handling that prevents data loss, or an explicit requirement. Do not expand scope merely because an adjacent improvement is attractive.
+
+Keep the response clean. Add an `Overlooked` or `Strongest unasked question` note only when it contains material information; do not emit empty ritual or boilerplate. Give concise conclusions, evidence, assumptions, and verification results. Do not reveal private chain-of-thought.
+
+Do not run the full Necktie Loop unless the user invokes `/necktie`, `$necktie`, `@necktie`, or explicitly requests the Necktie workflow. The full loop is: frame, baseline, critique, reverse, execute, review, verify.

package/.qoder-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "name": "necktie",
+  "version": "0.2.0",
+  "description": "Necktie Core on every response, plus an explicit bounded review loop.",
+  "author": { "name": "gillcash", "url": "https://github.com/gillcash" },
+  "homepage": "https://github.com/gillcash/necktie",
+  "repository": "https://github.com/gillcash/necktie",
+  "license": "MIT",
+  "keywords": ["agent-loop", "review", "verification"],
+  "skills": "./skills/",
+  "rules": "./.qoder/rules/",
+  "hooks": "./hooks/qoder-hooks.json"
+}

package/AGENTS.md

@@ -0,0 +1,18 @@
+# Necktie Core
+
+Necktie is active for every response.
+
+Before acting, align the requested output with the user's real goal, intended reader, acceptance criteria, constraints, available evidence, and authority. Make the smallest intervention that fully satisfies those conditions. Reuse trusted sources and native capabilities before adding new machinery.
+
+Before the final response:
+
+1. Check the work in proportion to its risk. Correct material errors that you can resolve.
+2. Identify any material consideration the user may have overlooked relative to the goal.
+3. Identify the strongest unasked question that a genuine subject-matter expert would ask, but include it only when its answer could change the decision, result, or risk.
+4. Ask the user a question only when the answer would materially change the objective, evidence, authority, or deliverable. Otherwise state the necessary assumption and proceed.
+
+Never trade away security, privacy, accessibility, input validation at trust boundaries, error handling that prevents data loss, or an explicit requirement. Do not expand scope merely because an adjacent improvement is attractive.
+
+Keep the response clean. Add an `Overlooked` or `Strongest unasked question` note only when it contains material information; do not emit empty ritual or boilerplate. Give concise conclusions, evidence, assumptions, and verification results. Do not reveal private chain-of-thought.
+
+Do not run the full Necktie Loop unless the user invokes `/necktie`, `$necktie`, `@necktie`, or explicitly requests the Necktie workflow. The full loop is: frame, baseline, critique, reverse, execute, review, verify.

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 DietrichGebert
+Copyright (c) 2026 gillcash
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/NOTICE

@@ -0,0 +1,7 @@
+Necktie 0.2.0
+Copyright (c) 2026 gillcash
+
+This project was structurally derived from Ponytail by Dietrich Gebert. It retains portions of Ponytail's cross-host packaging, adapter patterns, and test architecture under the MIT License. Necktie's behavior, workflow, documentation, branding, and command surface have been substantially rewritten.
+
+Ponytail: https://github.com/DietrichGebert/ponytail
+Copyright (c) 2026 Dietrich Gebert

package/README.es.md

@@ -0,0 +1,84 @@
+<p align="center"><img src="assets/logo-dark.png" width="220" alt="Logotipo de Necktie"></p>
+
+<h1 align="center">Necktie</h1>
+
+<p align="center"><em>the angel of late-stage capitalism for your AI agent</em></p>
+
+Necktie añade una revisión breve a cada respuesta del agente y ofrece un flujo explícito y limitado para trabajo importante. Invoque `/necktie` para encuadrar, establecer una línea base, criticar, revertir, ejecutar, revisar y verificar un objetivo.
+
+## Distinga las dos capas
+
+| Capa | Activación | Resultado |
+| --- | --- | --- |
+| Necktie Core | En cada respuesta, mediante el mecanismo nativo del host | Comprueba el objetivo y el trabajo, corrige errores materiales e identifica omisiones y la pregunta experta no formulada más importante |
+| Necktie Loop | Solo con `/necktie`, `$necktie`, `@necktie` o una petición explícita | Ejecuta siete fases con cuatro skills y una puerta de revisión finita |
+
+Necktie no usa un modo de encendido o apagado, un servicio de fondo ni niveles persistentes. Desinstale o desactive el plugin para dejar de usar Core.
+
+## Ejecute el ejemplo
+
+```text
+/necktie Evalúa la fiabilidad de los datos KPI de una tienda de alquiler de herramientas y equipos. Crea un plan de controles apto para decisiones a partir de evidencia admisible y verifica cada afirmación material.
+```
+
+```text
+frame -> baseline -> critique -> reverse -> execute -> review -> verify
+                                                   ^          |
+                                                   |          v
+                                                 revise <- REVISE
+```
+
+Las decisiones son `APPROVE`, `REVISE` y `BLOCK`. El ciclo se detiene después de tres decisiones de revisión, cuando el mismo problema sobrevive tres revisiones consecutivas o cuando falta evidencia, autoridad o una decisión material del usuario.
+
+## Instale Necktie
+
+### Claude Code
+
+```text
+/plugin marketplace add gillcash/necktie
+/plugin install necktie@necktie
+```
+
+### Codex
+
+```bash
+codex plugin marketplace add gillcash/necktie
+codex plugin add necktie@necktie
+```
+
+Abra `/hooks`, revise y autorice los hooks, y después inicie un hilo nuevo.
+
+### Otros hosts
+
+| Host | Instalación o mecanismo |
+| --- | --- |
+| GitHub Copilot CLI | `copilot plugin marketplace add gillcash/necktie`, luego `copilot plugin install necktie@necktie` |
+| Pi | `pi install git:github.com/gillcash/necktie` |
+| OpenCode | `{"plugin":["@gillcash/necktie"]}` |
+| Gemini CLI | `gemini extensions install https://github.com/gillcash/necktie` |
+| Antigravity | `agy plugin install https://github.com/gillcash/necktie` |
+| Hermes | `hermes plugins install gillcash/necktie --enable` |
+| Devin | `devin plugins install gillcash/necktie` |
+| Grok Build | `grok plugin install gillcash/necktie --trust` |
+| Swival | `swival skills add --global https://github.com/gillcash/necktie` |
+| OpenClaw | Instale los cuatro skills desde `.openclaw/skills/` o ClawHub |
+
+Cursor, Windsurf, Cline, Copilot Chat, Kiro, Qoder, Aider, Zed, CodeWhale, Junie, Amp y Jules usan el archivo de reglas correspondiente incluido en el repositorio. Consulte [la documentación de hosts](docs/host-support.md). Una regla estática proporciona Core, pero no crea comandos.
+
+## Use los cuatro skills
+
+- `necktie`: controla el ciclo completo.
+- `necktie-critique`: cuestiona la consulta y las omisiones materiales.
+- `necktie-reverse`: compila el recorrido en una instrucción ejecutable independiente.
+- `necktie-review`: devuelve `APPROVE`, `REVISE` o `BLOCK`.
+
+## Valide el proyecto
+
+```bash
+npm run build:adapters
+npm test
+```
+
+`core/necktie-core.md` es la única fuente de las reglas generadas. El proyecto conserva la atribución de la base de adaptadores Ponytail en [NOTICE](NOTICE) y usa la [licencia MIT](LICENSE).
+
+Esta documentación sigue principalmente una práctica orientada a ISO 24495-1 para las tareas del lector y se complementa con controles orientados a ASD-STE100 para términos, comandos, condiciones y estados. Esto no es una declaración de conformidad.

package/README.ko.md

@@ -0,0 +1,84 @@
+<p align="center"><img src="assets/logo-dark.png" width="220" alt="Necktie 로고"></p>
+
+<h1 align="center">Necktie</h1>
+
+<p align="center"><em>the angel of late-stage capitalism for your AI agent</em></p>
+
+Necktie는 에이전트의 모든 응답에 간결한 품질 점검을 적용하고, 중요한 작업을 위한 명시적이고 제한된 워크플로를 제공합니다. `/necktie`를 호출하면 목표를 프레임하고, 기준안을 만들고, 비평하고, 역설계하고, 실행하고, 검토하고, 검증합니다.
+
+## 두 계층을 구분하십시오
+
+| 계층 | 실행 시점 | 결과 |
+| --- | --- | --- |
+| Necktie Core | 호스트의 기본 훅 또는 지침 메커니즘을 통해 모든 응답에서 실행 | 목표 적합성과 작업을 점검하고, 중요한 오류와 누락을 찾으며, 결과를 바꿀 수 있는 가장 중요한 미질문을 제시 |
+| Necktie Loop | `/necktie`, `$necktie`, `@necktie` 또는 명시적 요청이 있을 때만 실행 | 네 개의 스킬과 유한한 검토 게이트로 일곱 단계를 실행 |
+
+Necktie는 켜기/끄기 모드, 백그라운드 서비스 또는 지속적인 강도 수준을 사용하지 않습니다. Core를 사용하지 않으려면 플러그인을 제거하거나 비활성화하십시오.
+
+## 예제를 실행하십시오
+
+```text
+/necktie 공구 및 장비 대여점의 KPI 데이터 신뢰성을 평가하십시오. 적격 증거를 사용해 의사결정용 통제 계획을 만들고 모든 중요한 주장을 검증하십시오.
+```
+
+```text
+frame -> baseline -> critique -> reverse -> execute -> review -> verify
+                                                   ^          |
+                                                   |          v
+                                                 revise <- REVISE
+```
+
+검토 결정은 `APPROVE`, `REVISE`, `BLOCK`입니다. 세 번의 수정 결정이 기록되거나, 같은 문제가 세 번 연속 남거나, 새로운 증거·권한·중요한 사용자 결정이 필요하면 루프가 중지됩니다.
+
+## Necktie를 설치하십시오
+
+### Claude Code
+
+```text
+/plugin marketplace add gillcash/necktie
+/plugin install necktie@necktie
+```
+
+### Codex
+
+```bash
+codex plugin marketplace add gillcash/necktie
+codex plugin add necktie@necktie
+```
+
+`/hooks`를 열어 훅을 검토하고 신뢰한 다음 새 스레드를 시작하십시오.
+
+### 다른 호스트
+
+| 호스트 | 설치 또는 메커니즘 |
+| --- | --- |
+| GitHub Copilot CLI | `copilot plugin marketplace add gillcash/necktie` 후 `copilot plugin install necktie@necktie` |
+| Pi | `pi install git:github.com/gillcash/necktie` |
+| OpenCode | `{"plugin":["@gillcash/necktie"]}` |
+| Gemini CLI | `gemini extensions install https://github.com/gillcash/necktie` |
+| Antigravity | `agy plugin install https://github.com/gillcash/necktie` |
+| Hermes | `hermes plugins install gillcash/necktie --enable` |
+| Devin | `devin plugins install gillcash/necktie` |
+| Grok Build | `grok plugin install gillcash/necktie --trust` |
+| Swival | `swival skills add --global https://github.com/gillcash/necktie` |
+| OpenClaw | `.openclaw/skills/` 또는 ClawHub에서 네 스킬 설치 |
+
+Cursor, Windsurf, Cline, Copilot Chat, Kiro, Qoder, Aider, Zed, CodeWhale, Junie, Amp, Jules는 저장소에 포함된 해당 규칙 파일을 사용합니다. [호스트 문서](docs/host-support.md)를 참조하십시오. 정적 규칙은 Core를 제공하지만 슬래시 명령을 만들지는 않습니다.
+
+## 네 스킬을 사용하십시오
+
+- `necktie`: 전체 루프를 제어합니다.
+- `necktie-critique`: 질문과 중요한 누락을 비평합니다.
+- `necktie-reverse`: 반복 과정을 독립 실행 가능한 지침으로 컴파일합니다.
+- `necktie-review`: `APPROVE`, `REVISE`, `BLOCK` 중 하나를 반환합니다.
+
+## 프로젝트를 검증하십시오
+
+```bash
+npm run build:adapters
+npm test
+```
+
+`core/necktie-core.md`는 생성 규칙의 단일 원본입니다. 프로젝트는 [NOTICE](NOTICE)에 Ponytail 어댑터 기반의 귀속을 보존하며 [MIT 라이선스](LICENSE)를 사용합니다.
+
+이 문서는 독자 작업을 위해 ISO 24495-1 지향 방식을 주로 사용하고, 용어·명령·조건·상태를 위해 ASD-STE100 지향 통제를 보완적으로 사용합니다. 이는 적합성 선언이 아닙니다.

package/README.md

@@ -0,0 +1,232 @@
+<p align="center">
+  <img src="assets/logo-dark.png" width="220" alt="Necktie logo">
+</p>
+
+<h1 align="center">Necktie</h1>
+
+<p align="center"><em>the angel of late-stage capitalism for your AI agent</em></p>
+
+Necktie adds a compact quality check to every agent response and provides an explicit, bounded workflow for consequential work. Invoke `/necktie` to frame, baseline, critique, reverse, execute, review, and verify a goal.
+
+## Know the two layers
+
+| Layer | When it runs | What it does |
+| --- | --- | --- |
+| Necktie Core | Every response, through the host's native hook or instruction mechanism | Checks goal fit and work quality, corrects material errors, surfaces material omissions, and asks the strongest unasked expert question when it matters |
+| Necktie Loop | Only after `/necktie`, `$necktie`, `@necktie`, or an explicit request | Runs the seven-phase workflow with four cooperating skills and a finite review gate |
+
+Necktie does not use an on/off mode, background service, or persistent operating level. Remove or disable the plugin when you do not want Necktie Core.
+
+## Use the portable plugin
+
+The root `plugin.json` targets the [Agent Plugins 1.0.0 specification](https://agent-plugins.org/). The portable layer contains the four skills in the standard `skills/` location. Host-specific lifecycle hooks, commands, and rule files extend that interoperability floor without changing the portable skill definitions.
+
+`necktie-mcp/` is an optional retrieval fallback. It is not required by the plugin or loop, and MCP alone does not make Core active on every response.
+
+## Run the loop
+
+```text
+/necktie Assess KPI data reliability for a tool and equipment rental store. Build a decision-ready control plan from eligible evidence and verify every material claim.
+```
+
+On a skill-oriented host, use:
+
+```text
+$necktie Assess KPI data reliability for a tool and equipment rental store. Build a decision-ready control plan from eligible evidence and verify every material claim.
+```
+
+The loop returns the requested artifact, a reusable execution brief, a review decision, a verification record, known limitations, and the strongest unasked question when it could affect action.
+
+## Follow the seven phases
+
+```text
+frame -> baseline -> critique -> reverse -> execute -> review -> verify
+                                                   ^          |
+                                                   |          v
+                                                 revise <- REVISE
+```
+
+| Phase | Required result |
+| --- | --- |
+| Frame | Outcome, reader, scope, constraints, source classes, and acceptance criteria |
+| Baseline | Smallest plausible approach and its assumptions |
+| Critique | Material omissions, framing defects, evidence needs, and strongest unasked question |
+| Reverse | One self-contained execution brief for a fresh session |
+| Execute | Candidate built from eligible raw evidence |
+| Review | Independent `APPROVE`, `REVISE`, or `BLOCK` decision |
+| Verify | Test, render, calculation, or inspection in the intended environment |
+
+`REVISE` returns the candidate to the author. The loop stops after three revision decisions, after the same unresolved issue appears in three consecutive reviews, or when a material blocker requires new evidence, authority, or user direction.
+
+## Install
+
+Node.js must be available to hosts that run the lifecycle hook. Review third-party hooks before you trust them.
+
+### Claude Code
+
+Send these as separate commands:
+
+```text
+/plugin marketplace add gillcash/necktie
+/plugin install necktie@necktie
+```
+
+### Codex
+
+```bash
+codex plugin marketplace add gillcash/necktie
+codex plugin add necktie@necktie
+```
+
+Start Codex, open `/hooks`, review and trust the Necktie hooks, and start a new thread. The same installation applies to the Codex desktop app after restart.
+
+### GitHub Copilot CLI
+
+```bash
+copilot plugin marketplace add gillcash/necktie
+copilot plugin install necktie@necktie
+```
+
+Copilot namespaces commands. For example, use `/necktie:necktie` and `/necktie:necktie-review`.
+
+### Pi
+
+```bash
+pi install git:github.com/gillcash/necktie
+```
+
+### OpenCode
+
+Use the published package:
+
+```json
+{ "plugin": ["@gillcash/necktie"] }
+```
+
+Or use a checkout:
+
+```json
+{ "plugin": ["./.opencode/plugins/necktie.mjs"] }
+```
+
+The OpenCode adapter injects Core on each turn and registers all four commands and skills.
+
+### Gemini CLI and Antigravity
+
+```bash
+gemini extensions install https://github.com/gillcash/necktie
+```
+
+```bash
+agy plugin install https://github.com/gillcash/necktie
+```
+
+These hosts use `AGENTS.md` as the always-on context and load the bundled skills through the extension.
+
+### Qoder
+
+Run Qoder from a checkout or copy `.qoder/rules/necktie.md` into the target project's `.qoder/rules/`. For hook-based per-prompt and subagent injection, install `hooks/qoder-hooks.json` in the project's Qoder settings and replace the plugin-root placeholder with the absolute checkout path if required by that host version.
+
+### Hermes Agent
+
+```bash
+hermes plugins install gillcash/necktie --enable
+```
+
+Restart Hermes. It injects Core before each model call and registers `necktie:<skill>` plus the four slash commands.
+
+### Swival
+
+```bash
+swival skills add --global https://github.com/gillcash/necktie
+swival skills add necktie
+```
+
+Use `$necktie` to invoke the loop. Copy `AGENTS.md` to the project or global Swival instructions location for Core.
+
+### Devin CLI
+
+```bash
+devin plugins install gillcash/necktie
+```
+
+Use `/necktie:necktie`, `/necktie:necktie-critique`, `/necktie:necktie-reverse`, or `/necktie:necktie-review`.
+
+### OpenClaw
+
+```bash
+clawhub install necktie
+clawhub install necktie-critique
+clawhub install necktie-reverse
+clawhub install necktie-review
+```
+
+Without ClawHub, copy the required directories from `.openclaw/skills/` into `~/.openclaw/skills/`. Install the Core rule separately as `AGENTS.md` when the host does not keep a skill active on every response.
+
+### Grok Build
+
+```bash
+grok plugin install gillcash/necktie --trust
+```
+
+Enable `necktie` in `/plugins`, then start a new session. Grok exposes the four skills. Its plugin lifecycle cannot inject Core reliably on every response, so use the repository `AGENTS.md` in the project for the always-on layer.
+
+### Static-rule hosts
+
+Necktie covers the remaining Ponytail-supported hosts through their persistent instruction file:
+
+| Host | Install this file |
+| --- | --- |
+| Cursor | `.cursor/rules/necktie.mdc` |
+| Windsurf | `.windsurf/rules/necktie.md` |
+| Cline | `.clinerules/necktie.md` |
+| GitHub Copilot Chat | `.github/copilot-instructions.md` |
+| Kiro | `.kiro/steering/necktie.md` |
+| Qoder | `.qoder/rules/necktie.md` |
+| Aider, Zed, CodeWhale, Amp, Jules | `AGENTS.md` |
+| Junie | `AGENTS.md`, selected as the project guidelines file |
+
+These adapters provide Core on every response when the host honors the installed rule. A static rule does not create slash commands; invoke the loop in plain language or install the four skills through that host's skill mechanism.
+
+See [docs/host-support.md](docs/host-support.md) for adapter boundaries and verification checks.
+
+## Use the four skills
+
+- `necktie` controls the complete loop.
+- `necktie-critique` challenges the inquiry and exposes material blind spots.
+- `necktie-reverse` compiles the successful trajectory into a fresh-session brief.
+- `necktie-review` returns an independent `APPROVE`, `REVISE`, or `BLOCK` decision.
+
+The Core can recommend a material next step, but it must not silently launch the full loop.
+
+## Keep an auditable run packet
+
+Most runs need no file. Create a packet only when the work must be resumable or auditable:
+
+```bash
+python skills/necktie/scripts/necktie_loop.py init --goal "Assess KPI data reliability for a tool and equipment rental store" --output .necktie/run.json
+python skills/necktie/scripts/necktie_loop.py transition --file .necktie/run.json --to baseline --note "Sources classified"
+python skills/necktie/scripts/necktie_loop.py show --file .necktie/run.json
+python skills/necktie-review/scripts/validate_review.py review.json
+```
+
+The Python scripts use only the standard library. They record states, decisions, and verification evidence, not private reasoning.
+
+## Develop and validate
+
+```bash
+npm run build:adapters
+npm test
+python C:/Users/you/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/necktie
+python C:/Users/you/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py .
+```
+
+`core/necktie-core.md` is the single source for generated instruction adapters. Do not edit generated copies directly.
+
+This README is governed primarily by ISO 24495-1-oriented plain-language practice because its intended readers must install, invoke, evaluate, and safely modify Necktie, misunderstanding could cause invalid setup, unintended workflow activation, weakened review independence, or unreliable deliverables, and the document requires both reader-level organization and technical semantic control. It is supplemented by ASD-STE100-oriented controls for consistent terms, commands, conditions, status values, and stopping rules.
+
+This is a writing profile, not a claim of conformity. See [docs/process-provenance.md](docs/process-provenance.md) for the generalized design provenance and source boundaries.
+
+## License
+
+Necktie is available under the [MIT License](LICENSE). [NOTICE](NOTICE) preserves attribution for the inherited Ponytail adapter foundation.

package/commands/necktie-critique.toml

@@ -0,0 +1,2 @@
+description = "Challenge an inquiry and surface material blind spots"
+prompt = "Use $necktie-critique on: {{args}}. Test goal alignment, assumptions, evidence needs, and the strongest unasked expert question."

package/commands/necktie-reverse.toml

@@ -0,0 +1,2 @@
+description = "Compile iterative context into one executable brief"
+prompt = "Use $necktie-reverse on: {{args}}. Produce a self-contained brief that can be executed in a fresh session from raw evidence."

package/commands/necktie-review.toml

@@ -0,0 +1,2 @@
+description = "Independently gate a candidate deliverable"
+prompt = "Use $necktie-review on: {{args}}. Judge the exact candidate against its brief, evidence, criteria, and verification; return APPROVE, REVISE, or BLOCK."

package/commands/necktie.toml

@@ -0,0 +1,2 @@
+description = "Run the explicit, bounded Necktie Loop"
+prompt = "Use $necktie for this goal: {{args}}. Frame, baseline, critique, reverse, execute, review, and verify. Return the final deliverable, reusable execution brief, verification record, material overlooked consideration, and strongest unasked question."

package/core/necktie-core.md

@@ -0,0 +1,18 @@
+# Necktie Core
+
+Necktie is active for every response.
+
+Before acting, align the requested output with the user's real goal, intended reader, acceptance criteria, constraints, available evidence, and authority. Make the smallest intervention that fully satisfies those conditions. Reuse trusted sources and native capabilities before adding new machinery.
+
+Before the final response:
+
+1. Check the work in proportion to its risk. Correct material errors that you can resolve.
+2. Identify any material consideration the user may have overlooked relative to the goal.
+3. Identify the strongest unasked question that a genuine subject-matter expert would ask, but include it only when its answer could change the decision, result, or risk.
+4. Ask the user a question only when the answer would materially change the objective, evidence, authority, or deliverable. Otherwise state the necessary assumption and proceed.
+
+Never trade away security, privacy, accessibility, input validation at trust boundaries, error handling that prevents data loss, or an explicit requirement. Do not expand scope merely because an adjacent improvement is attractive.
+
+Keep the response clean. Add an `Overlooked` or `Strongest unasked question` note only when it contains material information; do not emit empty ritual or boilerplate. Give concise conclusions, evidence, assumptions, and verification results. Do not reveal private chain-of-thought.
+
+Do not run the full Necktie Loop unless the user invokes `/necktie`, `$necktie`, `@necktie`, or explicitly requests the Necktie workflow. The full loop is: frame, baseline, critique, reverse, execute, review, verify.

package/hooks/copilot-hooks.json

@@ -0,0 +1,13 @@
+{
+  "version": 1,
+  "hooks": {
+    "sessionStart": [
+      {
+        "type": "command",
+        "bash": "node \"${PLUGIN_ROOT}/hooks/necktie-context.js\" SessionStart copilot",
+        "powershell": "node \"${PLUGIN_ROOT}\\hooks\\necktie-context.js\" SessionStart copilot",
+        "timeoutSec": 10
+      }
+    ]
+  }
+}

package/hooks/hooks.json

@@ -0,0 +1,27 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup|resume|clear|compact",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node -e \"const r=process.argv[1],e=process.argv[2],g=e&&!e.startsWith('$'+'{')?e:'',p=g||r;require(p+'/hooks/necktie-context.js').main(['SessionStart',g])\" \"${CLAUDE_PLUGIN_ROOT}\" \"${extensionPath}\"",
+            "additionalContextLimit": 1200
+          }
+        ]
+      }
+    ],
+    "SubagentStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node -e \"const r=process.argv[1],e=process.argv[2],g=e&&!e.startsWith('$'+'{')?e:'',p=g||r;require(p+'/hooks/necktie-context.js').main(['SubagentStart',g])\" \"${CLAUDE_PLUGIN_ROOT}\" \"${extensionPath}\"",
+            "additionalContextLimit": 1200
+          }
+        ]
+      }
+    ]
+  }
+}