@ksuchoi216/ahe 0.1.7 → 0.1.10

package/.codex/hooks/ahe-hook.js

@@ -1,195 +0,0 @@
-#!/usr/bin/env node
-const AHE_DIRECTIVE_MARKER = "<ahe-mode>";
-
-const STATUS_TABLE_LINES = [
-  "   - Start the response with a concise status report table.",
-  "   - Use this consistent Markdown table format:",
-  "     | Item | Content |",
-  "     |---|---|",
-  "     | AGENTS.md | Exists/missing, purpose status, and any obvious issue. |",
-  "     | PRODUCT.md | Exists/missing, completion state, and whether product scope needs work. |",
-  "     | INSTRUCTIONS.md | Exists/missing, and whether instruction boundaries need work. |",
-  "     | feature-list.json | Valid/missing/invalid, unfinished feature summary, and all-done status. |",
-  "     | PROGRESS.md | Exists/missing and current session state. |",
-  "   - Keep the table short and readable.",
-  "   - Do not include the next step inside the table.",
-];
-
-const COMMON_ROUTING_LINES = [
-  "1. Run CodeGraph preflight before inspecting harness status:",
-  "   - Check whether the CodeGraph CLI is installed with `command -v codegraph`.",
-  "   - If the `codegraph` command is not installed, report `NOT INSTALLATION of codegraph`, skip `codegraph init` and `codegraph sync`, and continue with normal repo inspection.",
-  "   - If `.codegraph/` does not exist, run `codegraph init` before reviewing code.",
-  "   - If `.codegraph/` exists, run `codegraph sync` before reviewing code.",
-  "",
-  "2. Inspect current harness state before choosing a workflow:",
-  "   - Check `AGENTS.md`.",
-  "   - Check `docs/PRODUCT.md` and `docs/INSTRUCTIONS.md` as the product/specification source of truth.",
-  "   - Check `feature-list.json` as a derived tracker.",
-  "   - Check `PROGRESS.md`.",
-  "   - Use `ahe-thinker` as the internal decision layer before choosing the next action.",
-  "   - Before reading large harness files wholesale, let `ahe-thinker` run the `ahe-compression` size detector and call `ahe-compression` if compression is required.",
-  "",
-  "3. Review code through CodeGraph when available:",
-  "   - Prefer CodeGraph MCP or CodeGraph exploration for code review and impact context after the preflight command succeeds.",
-  "   - If CodeGraph is not installed, skip CodeGraph review and rely on normal repo inspection.",
-  "",
-  "4. Make the first response a simple harness engineering status report table before proceeding:",
-  ...STATUS_TABLE_LINES,
-];
-
-const AHE_PROGRESS_DIRECTIVE = [
-  AHE_DIRECTIVE_MARKER,
-  "AHE automatic operation activated.",
-  "",
-  "The user sent the exact AHE command. Operate as the Awesome Harness Engineering router:",
-  "",
-  ...COMMON_ROUTING_LINES,
-  "",
-  "5. Decide the next AHE workflow with `ahe-thinker`:",
-  "   - If no harness files exist, route to `$ahe-init`.",
-  "   - If `docs/PRODUCT.md` or `docs/INSTRUCTIONS.md` is missing or empty, classify the state as `harness engineering not enough`.",
-  "   - If `feature-list.json` is missing or invalid, generating an empty one from template is allowed, but do not write specific features until `docs/PRODUCT.md` and `docs/INSTRUCTIONS.md` are created and organized.",
-  "   - If any feature in `feature-list.json` has a status other than `done`, classify the state as `in the middle of building features` and continue the first unfinished feature whose dependencies are satisfied.",
-  "   - If all features are `done` and no obvious harness gap remains, classify the state as `completed all` and ask the user for the next task.",
-  "   - Call `ahe-reviewer` when repo or code understanding is needed.",
-  "   - Call `ahe-conversator` when the next safe step is blocked on user input.",
-  "   - Call `ahe-harness` when product docs, instructions, tracking, todo sync, or compression-aware harness maintenance must change.",
-  "   - Call `ahe-solver` when the next job is solving or planning a feature.",
-  "",
-  "6. After the table, classify the harness into exactly one state.",
-  "   - Use exactly one state: `harness engineering not enough`, `in the middle of building features`, or `completed all`.",
-  "   - Do not include the next step inside the table.",
-  "   - Continue automatically after classification.",
-];
-
-const AHE_INIT_DIRECTIVE = [
-  AHE_DIRECTIVE_MARKER,
-  "AHE automatic operation activated.",
-  "",
-  "The user sent the exact AHE init command. Treat this as a possible new start request:",
-  "",
-  "1. Route to `$ahe-init` first.",
-  "2. If no AHE-managed harness files exist, start initialization normally.",
-  "3. If any AHE-managed harness file exists, read the existing files, summarize the current project purpose and product specification state, and ask what restart scope the user wants.",
-  "4. Do not remove, overwrite, or refresh existing harness files before the user answers the restart-scope question.",
-  "5. If the chosen restart scope replaces prior harness history, summarize that replaced state in the refreshed tracking artifacts instead of creating backup copies.",
-  "6. Interpret the restart scope from the user's free-form answer; examples like `purpose` and `product` are not a closed list.",
-  "7. Product/instructions specification details belong in `docs/PRODUCT.md` and `docs/INSTRUCTIONS.md`, not `AGENTS.md`.",
-  "8. After setup, call `ahe-harness` to build the initial product, instructions, and tracking state.",
-  "9. Use `ahe-thinker` before clarification when the next setup step is uncertain.",
-  "10. If clarification is needed, call `ahe-conversator` for the exact missing detail.",
-].join("\n");
-
-function getQueryDirective(prompt) {
-  return [
-    AHE_DIRECTIVE_MARKER,
-    "AHE automatic operation activated.",
-    "",
-    `Original prompt: "${prompt}"`,
-    "",
-    "The user sent an explicit AHE query. Route it through `ahe-thinker`:",
-    "",
-    ...COMMON_ROUTING_LINES,
-    "",
-    "5. Decide the next AHE workflow with `ahe-thinker` based on the original prompt:",
-    "   - Use `ahe-reviewer` for code or harness review work.",
-    "   - Use `ahe-harness` for product, instructions, progress, feature-list, todo, or compression maintenance.",
-    "   - For `ahe compress feature-list`, replace old completed feature entries with one summarized done feature, preserve unfinished details, and reconcile `feature-list.json` against `docs/PRODUCT.md`.",
-    "   - If no new feature can be derived from `docs/PRODUCT.md`, call `ahe-conversator` to ask what next feature, product direction, or goal should be tracked.",
-    "   - Use `ahe-solver` for feature-solving work.",
-    "   - If multiple plausible next steps remain, use `ahe-conversator` to ask the minimum question needed.",
-    "",
-    "6. After the table, classify the harness into exactly one state.",
-    "   - Use exactly one state: `harness engineering not enough`, `in the middle of building features`, or `completed all`.",
-    "   - Do not include the next step inside the table.",
-    "   - Continue automatically after classification.",
-  ].join("\n");
-}
-
-function normalizePrompt(prompt) {
-  return prompt.trim().toLowerCase();
-}
-
-function isExactAheCommand(prompt) {
-  return normalizePrompt(prompt) === "ahe";
-}
-
-function isExactAheInitCommand(prompt) {
-  const normalizedPrompt = normalizePrompt(prompt);
-  return (
-    normalizedPrompt === "ahe init" ||
-    normalizedPrompt === "ahe-init" ||
-    normalizedPrompt === "$ahe-init"
-  );
-}
-
-function isExplicitAheQuery(prompt) {
-  const normalizedPrompt = normalizePrompt(prompt);
-  if (isExactAheCommand(prompt) || isExactAheInitCommand(prompt)) {
-    return false;
-  }
-  return normalizedPrompt.startsWith("ahe ");
-}
-
-async function main() {
-  let raw = "";
-  process.stdin.setEncoding("utf8");
-  for await (const chunk of process.stdin) {
-    raw += chunk;
-  }
-
-  if (!raw.trim()) {
-    return;
-  }
-
-  let parsed;
-  try {
-    parsed = JSON.parse(raw);
-  } catch {
-    return;
-  }
-
-  if (
-    parsed &&
-    parsed.hook_event_name === "UserPromptSubmit" &&
-    typeof parsed.prompt === "string"
-  ) {
-    if (isExactAheCommand(parsed.prompt)) {
-      process.stdout.write(
-        JSON.stringify({
-          hookSpecificOutput: {
-            hookEventName: "UserPromptSubmit",
-            additionalContext: AHE_PROGRESS_DIRECTIVE.join("\n"),
-          },
-        }) + "\n"
-      );
-      return;
-    }
-
-    if (isExactAheInitCommand(parsed.prompt)) {
-      process.stdout.write(
-        JSON.stringify({
-          hookSpecificOutput: {
-            hookEventName: "UserPromptSubmit",
-            additionalContext: AHE_INIT_DIRECTIVE,
-          },
-        }) + "\n"
-      );
-      return;
-    }
-
-    if (isExplicitAheQuery(parsed.prompt)) {
-      process.stdout.write(
-        JSON.stringify({
-          hookSpecificOutput: {
-            hookEventName: "UserPromptSubmit",
-            additionalContext: getQueryDirective(parsed.prompt),
-          },
-        }) + "\n"
-      );
-    }
-  }
-}
-
-main().catch(() => {});

package/.codex/skills/ahe-harness/SKILL.md

@@ -1,115 +0,0 @@
----
-name: ahe-harness
-description: Internal AHE harness workflow for managing product docs, instructions, feature tracking, session artifacts, todo sync, and compression-aware maintenance.
----
-
-# AHE Harness
-
-This is an internal AHE workflow skill, not a user-facing command.
-
-Do not treat `$ahe-harness` as a user command.
-Use it when `ahe-thinker` or another worker decides that harness artifacts must
-be created, updated, reconciled, or compressed.
-
-## Command Workflow: ahe-harness
-
-### Harness Inspection
-
-- Read `docs/PRODUCT.md` if it exists.
-- Read `docs/INSTRUCTIONS.md` if it exists.
-- Read `AGENTS.md`, `feature-list.json`, `PROGRESS.md`, `SESSION-HANDOFF.md`,
-  and `docs/todo.md` when they exist.
-- Read `.ahe/process_status.json` when it exists.
-- Treat `docs/PRODUCT.md` as the canonical source of truth and
-  `feature-list.json` as a derived tracker.
-
-### Harness Decision Paths
-
-- Clarify product goal, scope, and success criteria when `docs/PRODUCT.md`
-  needs to change.
-- Clarify project instructions when `docs/INSTRUCTIONS.md` needs to change.
-- Clarify what next feature or goal should be tracked when the next work item is
-  unclear.
-- `docs/PRODUCT.md` is the canonical home for product specification details collected during `ahe init`.
-- Write product behavior, scope, requirements, success criteria, and workflow details into `docs/PRODUCT.md`.
-- `docs/PRODUCT.md` is the canonical source of truth. Concrete feature items for `feature-list.json` must be derived from it only after it has been populated.
-- Do not move product specification details into `AGENTS.md`.
-- Update only the relevant docs among `docs/PRODUCT.md` and
-  `docs/INSTRUCTIONS.md`.
-- If the user is adding new work, append it into the last `## TODO` section of
-  `docs/todo.md`, create that section when needed, and update
-  `feature-list.json`.
-- Apply the queued `docs/todo.md` content to `docs/PRODUCT.md`.
-- Remove the applied content from `docs/todo.md` because that todo content is
-  already reflected in `docs/PRODUCT.md`.
-- Update `feature-list.json` to derive the specific feature items from the updated `docs/PRODUCT.md`.
-- Update `PROGRESS.md`.
-- Update `SESSION-HANDOFF.md`.
-- For `ahe compress feature-list`, replace old completed feature entries with one summarized done feature.
-- Keep the summarized feature valid for the existing schema by preserving its
-  own `id`, `name`, `description`, `dependencies`, `status`, and short
-  evidence.
-- Preserve unfinished, blocked, or active feature items in full detail.
-- Reconcile `feature-list.json` against `docs/PRODUCT.md` after compression.
-- If no new feature can be derived from `docs/PRODUCT.md`, call `ahe-conversator` to ask what next feature, product direction, or goal should be tracked.
-- Call `ahe-reviewer` directly when code or progress evidence must be checked
-  before updating harness files.
-
-### Harness Completion
-
-- Keep `feature-list.json` valid JSON.
-- Do not create backup copies when compressing harness history.
-- Keep `PROGRESS.md` focused on current work, decisions that still matter,
-  blockers, and recent verification evidence.
-- Keep `SESSION-HANDOFF.md` focused on the next-session startup path.
-- Keep `.ahe/process_status.json` aligned with the active workflow.
-
-## Clarification Rule
-
-When the next harness step is not clear, follow the `ahe-thinker` protocol first. If `ahe-thinker` finds missing information, follow the `ahe-conversator` protocol. Ask again recursively using a Codex-supported structured response request, provide 2-3 meaningful mutually exclusive options
-when possible, and allow custom input when predefined options are not enough.
-
-### User Response Target
-
-- Collect the product, instruction, tracking, or next-feature details required
-  to update harness artifacts safely.
-
-### Questions to Ask
-
-- Ask who the product is for and what problem it solves when product intent is
-  unclear.
-- Ask what behavior, scope boundaries, and success criteria should be
-  documented.
-- Ask what rule, practice, or guideline belongs in `docs/INSTRUCTIONS.md`.
-- Ask what work should be added next when `docs/PRODUCT.md` does not imply a new
-  feature safely.
-
-### Clarification Criteria
-
-- The answer must be concrete enough to update the relevant harness files
-  without guessing.
-- The answer must describe actionable work, the affected area, and the intended
-  outcome when queuing a todo item.
-
-### Re-ask When
-
-- Ask again when the answer is vague, contradictory, or incomplete.
-- Ask again when the response names a topic without enough detail to update the
-  harness safely.
-
-## Session Tracking and Handoff Sync
-
-### Tracking Update Rules
-
-- Update `.ahe/process_status.json` at workflow start.
-- Update `.ahe/process_status.json` after every answered question.
-- Refresh `updated_at` every time workflow state changes.
-- Keep `current_command`, `current_step`, and `workflow_complete` aligned with the active workflow state.
-- Keep the `files` status map aligned with the actual workspace files.
-
-### Progress and Handoff Content Requirements
-
-- Update `PROGRESS.md` whenever the active feature, workflow status, blockers, or verification state changes.
-- Update `SESSION-HANDOFF.md` whenever the current objective, completed work, important files, verification evidence, or recommended next step changes.
-- PROGRESS.md must reflect the current active feature and latest completed work.
-- SESSION-HANDOFF.md must leave the next Codex session with a concrete startup path.

package/.codex/skills/ahe-reviewer/SKILL.md

@@ -1,35 +0,0 @@
----
-name: ahe-reviewer
-description: Internal AHE review workflow for understanding repo code, harness files, and CodeGraph context before another agent acts.
----
-
-# AHE Reviewer
-
-This is an internal AHE workflow skill, not a user-facing command.
-
-Do not treat `$ahe-reviewer` as a user command.
-Use it when `ahe-thinker` or another worker needs evidence from code or harness
-state before deciding what to do next.
-
-## Review Scope
-
-- Inspect repo code, harness files, verification history, and feature progress.
-- If `.codegraph/` exists, prefer `.codegraph` or CodeGraph-backed review
-  context when available.
-- Check `AGENTS.md`, `docs/PRODUCT.md`, `docs/INSTRUCTIONS.md`,
-  `feature-list.json`, `PROGRESS.md`, `SESSION-HANDOFF.md`, and `docs/todo.md`
-  when the question is about harness state.
-
-## Handoffs
-
-- Report findings back to `ahe-thinker` by default.
-- Call `ahe-harness` directly when review finds harness drift, stale tracking,
-  or Product.md / feature-list mismatches.
-- Call `ahe-conversator` only when the missing information must come from the
-  user.
-
-## Output
-
-- State what was reviewed.
-- State the relevant evidence or mismatch.
-- State the recommended next agent.

package/.codex/skills/ahe-solver/SKILL.md

@@ -1,24 +0,0 @@
----
-name: ahe-solver
-description: Internal AHE feature-solving workflow for dividing, planning, and solving feature work after the active goal is clear enough.
----
-
-# AHE Solver
-
-This is an internal AHE workflow skill, not a user-facing command.
-
-Do not treat `$ahe-solver` as a user command.
-Use it when `ahe-thinker` decides that the next job is building or planning a
-feature.
-
-## Command Workflow: ahe-solver
-
-- Read the active feature context from `docs/PRODUCT.md`, `feature-list.json`,
-  `PROGRESS.md`, and any relevant code files.
-- Divide broad work into smaller problems when useful.
-- Plan each smaller problem before implementation.
-- Call `ahe-reviewer` when repo or code understanding is needed.
-- Call `ahe-conversator` when feature requirements, scope, or success criteria
-  are still unclear.
-- Report the solved step, remaining work, and recommended next agent back to
-  `ahe-thinker`.

package/.codex/skills/ahe-thinker/SKILL.md

@@ -1,80 +0,0 @@
----
-name: ahe-thinker
-description: Internal AHE orchestration protocol for routing exact `ahe` and explicit `ahe <query>` requests through the AHE agent network.
----
-
-# AHE Thinker
-
-This is an internal AHE workflow skill, not a user-facing command.
-
-Do not treat `$ahe-thinker` as a user command.
-Use it as the central decision layer for AHE work.
-
-## Purpose
-
-- Judge what is missing before another agent acts.
-- Judge the active `project`, `feature`, or `sub-feature`.
-- Decide which of `Why`, `What`, and `How` are still missing.
-- Choose the next internal agent: `ahe-reviewer`, `ahe-conversator`,
-  `ahe-harness`, or `ahe-solver`.
-- Receive each agent result, reassess the state, and decide the next step.
-
-## Routing Inputs
-
-- Exact `ahe` means continue existing harness work.
-- Exact `ahe init`, exact `ahe-init`, and exact `$ahe-init` stay on the
-  `$ahe-init` path.
-- Explicit `ahe <query>` means route the query through `ahe-thinker`.
-- Broad non-prefixed prompts must not activate AHE.
-
-## Size Preflight
-
-- Before reading full harness files, run
-  `sh .codex/skills/ahe-compression/scripts/check-harness-size.sh`.
-- If the detector exits with `COMPRESSION_REQUIRED` or code `2`, call
-  `ahe-compression` before normal routing.
-- Do not read oversized harness files wholesale before compression routing is
-  settled.
-
-## Decision Rules
-
-- For a `project`, require `Why`, `What`, and `How` by default.
-- For a `feature` or `sub-feature`, require only the minimum of `Why`, `What`,
-  and `How` needed to proceed safely.
-- If the need is understanding repo code, harness drift, progress evidence, or
-  CodeGraph context, call `ahe-reviewer`.
-- If the need is user clarification, call `ahe-conversator`.
-- If the need is updating harness artifacts, product docs, feature tracking,
-  todo sync, or compression of completed history, call `ahe-harness`.
-- If the need is solving or decomposing feature work, call `ahe-solver`.
-
-## Interaction Model
-
-- `ahe-thinker` is centered, but direct worker-to-worker calls are allowed when
-  they are the obvious next step.
-- Typical loops:
-  - `ahe-thinker -> ahe-reviewer -> ahe-thinker`
-  - `ahe-thinker -> ahe-harness -> ahe-thinker`
-  - `ahe-thinker -> ahe-conversator -> ahe-thinker`
-  - `ahe-thinker -> ahe-solver -> ahe-thinker`
-- Allowed direct handoffs include:
-  - `ahe-harness -> ahe-conversator`
-  - `ahe-solver -> ahe-reviewer`
-  - `ahe-reviewer -> ahe-harness`
-- Every handoff must state the goal, reason, relevant files or context, and the
-  expected result.
-
-## Broad Intent Routing
-
-- Use `ahe-reviewer` for review-first requests.
-- Use `ahe-harness` for product, instructions, progress, feature-list, todo, or
-  compression maintenance.
-- Use `ahe-solver` for feature implementation planning or execution work.
-- Use `ahe-conversator` when no safe next step exists without user input.
-
-## Completion
-
-- Continue to the next skill or next unfinished feature until the active unit is
-  resolved.
-- Keep `docs/PRODUCT.md` as the canonical contract and `feature-list.json` as a
-  derived tracker.