@ksuchoi216/ahe 0.1.7 → 0.1.12

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

@@ -1,97 +0,0 @@
----
-name: ahe-compression
-description: Internal AHE compression workflow for detecting oversized harness-engineering files and compacting them before AHE thinker or harness routing reads large context. Use when AGENTS.md, docs/PRODUCT.md, docs/INSTRUCTIONS.md, feature-list.json, PROGRESS.md, SESSION-HANDOFF.md, docs/todo.md, or other AHE harness artifacts have too many lines or waste context.
----
-
-# AHE Compression
-
-This is an internal AHE workflow skill, not a user-facing command.
-
-Do not treat `$ahe-compression` as a user command.
-Use it after `ahe-thinker` or `ahe-harness` decides that harness context is too large to read
-efficiently.
-
-## Size Detection
-
-Run the deterministic line-count preflight before reading full harness files:
-
-```bash
-sh .codex/skills/ahe-compression/scripts/check-harness-size.sh
-```
-
-The script checks these AHE-managed files when they exist:
-
-- `AGENTS.md`
-- `docs/PRODUCT.md`
-- `docs/INSTRUCTIONS.md`
-- `feature-list.json`
-- `PROGRESS.md`
-- `SESSION-HANDOFF.md`
-- `docs/todo.md`
-
-Default thresholds are configured in `.codex/ahe-shared/config.yaml`:
-
-- `agent_md`: 80
-- `product_md`: 180
-- `instructions_md`: 180
-- `feature_list_json`: 180
-- `progress_md`: 180
-- `session_handoff_md`: 180
-- `todo_md`: 180
-- `total`: 750 (combined harness context limit)
-
-Override thresholds only when the workspace has an explicit local rule using environment variables (e.g., `AHE_AGENT_MD_LIMIT`, `AHE_FILE_LINE_LIMIT`, `AHE_TOTAL_LINE_LIMIT`):
-
-```bash
-AHE_AGENT_MD_LIMIT=100 AHE_TOTAL_LINE_LIMIT=900 sh .codex/skills/ahe-compression/scripts/check-harness-size.sh
-```
-
-Exit code meanings:
-
-- `0`: no compression needed.
-- `2`: compression needed.
-- Output ending in `COMPRESSION_REQUIRED`: compression needed.
-- Any other nonzero code: detector failed; fall back to `wc -l` on the same
-  file set and continue the decision manually.
-
-## Compression Decision
-
-- If the detector exits `2`, compress before normal AHE routing continues.
-- If only one file exceeds the per-file threshold, compress that file first.
-- If total harness context exceeds the total threshold, compress the largest
-  AHE-managed files until the total is under the threshold.
-- If `AGENTS.md` is oversized, obey the local `AGENTS.md` instructions before
-  editing it. Compress only sections that local rules allow. If no section is
-  safely editable, report the blocker and compress other harness files instead.
-- Do not read an oversized file wholesale after detection. Read headings,
-  current-status sections, JSON keys, or bounded line ranges needed to preserve
-  behavior.
-
-## Compression Rules
-
-- Preserve active requirements, current decisions, incomplete work, blockers,
-  dependencies, and verification evidence.
-- Preserve required headers and file formats for `PROGRESS.md`,
-  `SESSION-HANDOFF.md`, `feature-list.json`, and `AGENTS.md`.
-- Keep `feature-list.json` valid JSON. Replace stale completed-feature history
-  with one summarized done feature, preserve its `id`, `name`, `description`,
-  `dependencies`, `status`, and short evidence, and keep current unfinished
-  details as-is.
-- Keep `docs/PRODUCT.md` and `docs/INSTRUCTIONS.md` as the current harness
-  contract. Remove duplicate historical wording only when the active contract
-  remains clear.
-- Keep `PROGRESS.md` focused on current status, recent completed work,
-  decisions that still matter, blockers, and latest verification.
-- Keep `SESSION-HANDOFF.md` focused on the startup path for the next session,
-  important files, open questions, and current verification status.
-- Do not create backup copies when compressing harness history. Preserve useful
-  context through concise summaries in the refreshed harness files instead.
-
-## Completion
-
-- Re-run the size detector after compression.
-- Run JSON validation when `feature-list.json` changed.
-- Run the repository's normal harness verification command when compression
-  changed tracked harness files.
-- Update `PROGRESS.md` and `SESSION-HANDOFF.md` with the compression evidence
-  when they changed or when compression affects the active workflow.

package/.codex/skills/ahe-compression/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "AHE Compression"
-  short_description: "Compress oversized harness context"
-  default_prompt: "Use $ahe-compression to compact oversized AHE harness files before continuing."
-policy:
-  allow_implicit_invocation: false

package/.codex/skills/ahe-compression/scripts/check-harness-size.sh

@@ -1,109 +0,0 @@
-#!/usr/bin/env sh
-set -eu
-
-limit_agent_md=180
-limit_product_md=180
-limit_instructions_md=180
-limit_feature_list_json=180
-limit_progress_md=180
-limit_session_handoff_md=180
-limit_todo_md=180
-limit_total=750
-
-config_file=".codex/ahe-shared/config.yaml"
-if [ -f "${config_file}" ]; then
-  while IFS= read -r line || [ -n "$line" ]; do
-    line="${line#"${line%%[![:space:]]*}"}"
-    line="${line%"${line##*[![:space:]]}"}"
-    case "$line" in
-      "" | \#*) continue ;;
-    esac
-    
-    key="${line%%:*}"
-    val="${line#*:}"
-    key="${key%"${key##*[![:space:]]}"}"
-    val="${val#"${val%%[![:space:]]*}"}"
-    
-    case "$val" in
-      ''|*[!0-9]*) continue ;;
-    esac
-
-    case "$key" in
-      agent_md) limit_agent_md="$val" ;;
-      product_md) limit_product_md="$val" ;;
-      instructions_md) limit_instructions_md="$val" ;;
-      feature_list_json) limit_feature_list_json="$val" ;;
-      progress_md) limit_progress_md="$val" ;;
-      session_handoff_md) limit_session_handoff_md="$val" ;;
-      todo_md) limit_todo_md="$val" ;;
-      total) limit_total="$val" ;;
-    esac
-  done < "${config_file}"
-fi
-
-limit_agent_md="${AHE_AGENT_MD_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_agent_md}}"
-limit_product_md="${AHE_PRODUCT_MD_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_product_md}}"
-limit_instructions_md="${AHE_INSTRUCTIONS_MD_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_instructions_md}}"
-limit_feature_list_json="${AHE_FEATURE_LIST_JSON_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_feature_list_json}}"
-limit_progress_md="${AHE_PROGRESS_MD_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_progress_md}}"
-limit_session_handoff_md="${AHE_SESSION_HANDOFF_MD_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_session_handoff_md}}"
-limit_todo_md="${AHE_TODO_MD_LIMIT:-${AHE_FILE_LINE_LIMIT:-$limit_todo_md}}"
-total_limit="${AHE_TOTAL_LINE_LIMIT:-$limit_total}"
-
-total_lines=0
-compression_required=0
-
-if [ "$#" -eq 0 ]; then
-  set -- \
-    "AGENTS.md" \
-    "docs/PRODUCT.md" \
-    "docs/INSTRUCTIONS.md" \
-    "feature-list.json" \
-    "PROGRESS.md" \
-    "SESSION-HANDOFF.md" \
-    "docs/todo.md"
-fi
-
-for file_path in "$@"; do
-  if [ ! -f "${file_path}" ]; then
-    continue
-  fi
-
-  line_count="$(wc -l < "${file_path}")"
-  line_count="${line_count#"${line_count%%[![:space:]]*}"}"
-  line_count="${line_count%"${line_count##*[![:space:]]}"}"
-  total_lines=$((total_lines + line_count))
-
-  current_limit=180
-  case "${file_path}" in
-    "AGENTS.md") current_limit="${limit_agent_md}" ;;
-    "docs/PRODUCT.md") current_limit="${limit_product_md}" ;;
-    "docs/INSTRUCTIONS.md") current_limit="${limit_instructions_md}" ;;
-    "feature-list.json") current_limit="${limit_feature_list_json}" ;;
-    "PROGRESS.md") current_limit="${limit_progress_md}" ;;
-    "SESSION-HANDOFF.md") current_limit="${limit_session_handoff_md}" ;;
-    "docs/todo.md") current_limit="${limit_todo_md}" ;;
-    *) current_limit="${AHE_FILE_LINE_LIMIT:-180}" ;;
-  esac
-
-  if [ "${line_count}" -ge "${current_limit}" ]; then
-    compression_required=1
-    printf 'COMPRESS\t%s\t%s\tlimit=%s\n' "${file_path}" "${line_count}" "${current_limit}"
-  else
-    printf 'OK\t%s\t%s\tlimit=%s\n' "${file_path}" "${line_count}" "${current_limit}"
-  fi
-done
-
-if [ "${total_lines}" -ge "${total_limit}" ]; then
-  compression_required=1
-  printf 'COMPRESS_TOTAL\t%s\tlimit=%s\n' "${total_lines}" "${total_limit}"
-else
-  printf 'OK_TOTAL\t%s\tlimit=%s\n' "${total_lines}" "${total_limit}"
-fi
-
-if [ "${compression_required}" -eq 1 ]; then
-  printf 'COMPRESSION_REQUIRED\n'
-  exit 2
-fi
-
-printf 'COMPRESSION_NOT_REQUIRED\n'

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.