all-hands-cli 0.1.0

package/.allhands/schemas/prompt.yaml

@@ -0,0 +1,92 @@
+# Prompt File Schema
+# Single source of truth for prompt file structure
+
+frontmatter:
+  number:
+    type: integer
+    required: true
+    description: "Prompt execution order (01, 02, etc.)"
+
+  title:
+    type: string
+    required: true
+    description: "Human-readable task name"
+
+  type:
+    type: enum
+    required: true
+    values: [planned, emergent, user-patch, review-fix ]
+    default: planned
+    description: "Type of prompt (planned, emergent, user-patch, review-fix)"
+
+  status:
+    type: enum
+    required: true
+    values: [pending, in_progress, done]
+    default: pending
+    description: "Current execution state"
+
+  dependencies:
+    type: array
+    items: integer
+    default: []
+    description: "Prompt numbers that must complete first"
+
+  attempts:
+    type: integer
+    default: 0
+    description: "Number of execution attempts"
+
+  commits:
+    type: array
+    items: string
+    default: []
+    description: "Git commit hashes for work done on this prompt (chronological order, includes failed attempts)"
+
+  validation_suites:
+    type: array
+    items: string
+    default: []
+    description: "Paths to validation suite files elected for this prompt (e.g., .allhands/validation/typescript-typecheck.md)"
+
+  skills:
+    type: array
+    items: string
+    default: []
+    description: "Paths to skill files for domain expertise (e.g., .allhands/skills/building-expo-ui/SKILL.md)"
+
+  patches_prompts:
+    type: array
+    items: integer
+    default: []
+    description: "Prompt numbers this user-patch addresses (only valid for type: user-patch). References which prompts required user intervention."
+
+  uses_tdd_workflow:
+    type: boolean
+    default: false
+    description: "If true, this prompt used the TDD workflow"
+
+body:
+  description: "Markdown task instructions for the executing agent"
+  sections:
+    - name: "Tasks"
+      required: true
+      description: "List of 2-6 specific tasks to complete with implementation approach ideas and suggested instructions"
+
+    - name: "Acceptance Criteria"
+      required: true
+      description: "Validation requirements for completion"
+
+    - append_success_format: |
+        SUCCESS SUMMARY:
+        **Summary**: Brief explanation
+        **Limitations**: List of key limitations discovered that hindered implementation
+        **Decisions**: List of key decisions made that were open to make, or required to make in order to achieve the acceptance criteria
+        **Files**: List of key files affected
+        **Validation**: List of validation techniques that were used to achieve the acceptance criteria with detail on tests run, how they were run, and their results
+
+    - append_failure_format: |
+        FAILURE SUMMARY:
+        **Verdict**: Why the previous attempt was cleared for a blank slate, OR why the previous attempt was commited and expected to be built on top of
+        **Learnings**: What was learned in the attempt that failed
+        **Left to do**: Infered tips on how to keep going after failure

package/.allhands/schemas/skill.yaml

@@ -0,0 +1,34 @@
+# Skill Schema
+# Files in .allhands/skills/*/SKILL.md
+# Single source of truth for skill documentation
+
+frontmatter:
+  name:
+    type: string
+    required: true
+    description: "Unique skill identifier (must match containing folder name)"
+
+  description:
+    type: string
+    required: true
+    description: "Use case description - when/why to use this skill for domain expertise"
+
+  globs:
+    type: array
+    items: string
+    required: true
+    description: "File patterns this skill applies to (used for discovery during prompt curation)"
+
+  version:
+    type: string
+    required: false
+    description: "Semantic version of the skill"
+
+  license:
+    type: string
+    required: false
+    description: "License for the skill content"
+
+body:
+  description: "Domain expertise guide - how to apply this skill's knowledge"
+  sections: []  # No required sections - body is flexible

package/.allhands/schemas/solution.yaml

@@ -0,0 +1,131 @@
+# Solution Schema
+# Files in docs/solutions/<category>/<name>.md
+# Single source of truth for documented learnings and solved problems
+# Per **Knowledge Compounding**, solutions capture institutional knowledge for future reference
+
+frontmatter:
+  title:
+    type: string
+    required: true
+    description: "Descriptive title of the problem/solution (searchable)"
+
+  date:
+    type: string
+    required: true
+    format: "YYYY-MM-DD"
+    description: "Date the solution was documented"
+
+  milestone:
+    type: string
+    required: false
+    description: "Milestone branch name where this was discovered (if applicable)"
+
+  problem_type:
+    type: enum
+    required: true
+    values:
+      - build_error
+      - test_failure
+      - runtime_error
+      - performance_issue
+      - database_issue
+      - security_issue
+      - ui_bug
+      - integration_issue
+      - logic_error
+      - agentic_issue
+      - workflow_issue
+      - best_practice
+      - documentation_gap
+    description: "Category of problem - determines storage directory"
+
+  component:
+    type: string
+    required: true
+    description: "Technical component affected (e.g., 'api-client', 'auth-service', 'database', 'ui-component')"
+
+  symptoms:
+    type: array
+    items: string
+    required: true
+    min_items: 1
+    max_items: 5
+    description: "Observable symptoms that indicate this problem (searchable)"
+
+  root_cause:
+    type: enum
+    required: true
+    values:
+      - missing_dependency
+      - wrong_api_usage
+      - configuration_error
+      - logic_error
+      - timing_issue
+      - resource_leak
+      - missing_validation
+      - permission_issue
+      - agentic_hallucination
+      - agentic_duplication
+      - agentic_miscommunication
+      - incomplete_implementation
+      - environment_mismatch
+      - documentation_missing
+    description: "Root cause category for pattern detection"
+
+  severity:
+    type: enum
+    required: true
+    values: [critical, high, medium, low]
+    description: "Impact severity for prioritization"
+
+  tags:
+    type: array
+    items: string
+    required: true
+    description: "Searchable keywords (lowercase, hyphen-separated)"
+
+  source:
+    type: enum
+    required: false
+    values: [user-steering, agent-inferred, review-fix]
+    default: agent-inferred
+    description: "How this learning was discovered"
+
+body:
+  description: "Structured documentation of the problem and solution"
+  sections:
+    - name: "Problem"
+      required: true
+      description: "What happened - exact error messages, observable behavior"
+
+    - name: "Investigation"
+      required: false
+      description: "What was tried that didn't work (helps avoid wrong paths)"
+
+    - name: "Solution"
+      required: true
+      description: "What fixed it - code changes, configuration, etc."
+
+    - name: "Prevention"
+      required: true
+      description: "How to avoid this in future - patterns, checks, guidance"
+
+    - name: "Related"
+      required: false
+      description: "Cross-references to similar solutions"
+
+# Category mapping based on problem_type
+category_mapping:
+  build_error: "build-errors"
+  test_failure: "test-failures"
+  runtime_error: "runtime-errors"
+  performance_issue: "performance-issues"
+  database_issue: "database-issues"
+  security_issue: "security-issues"
+  ui_bug: "ui-bugs"
+  integration_issue: "integration-issues"
+  logic_error: "logic-errors"
+  agentic_issue: "agentic-issues"
+  workflow_issue: "workflow-issues"
+  best_practice: "best-practices"
+  documentation_gap: "documentation-gaps"

package/.allhands/schemas/spec.yaml

@@ -0,0 +1,67 @@
+# Spec Schema
+# Single source of truth for specification files
+
+frontmatter:
+  name:
+    type: string
+    required: true
+    description: "Spec name (used for branch naming, directory creation)"
+
+  domain_name:
+    type: string
+    required: true
+    description: "Domain name (used to group specs into initiatives)"
+
+  type:
+    type: enum
+    values: [milestone, investigation, optimization, refactor, documentation, triage]
+    default: milestone
+    description: "Spec type — determines workflow orchestration, scoping flows, and branch prefix conventions"
+
+  status:
+    type: enum
+    values: [roadmap, in_progress, completed]
+    default: roadmap
+    description: "Spec implementation status"
+
+  dependencies:
+    type: array
+    items: string
+    default: []
+    description: "Other spec names this depends on"
+
+  branch:
+    type: string
+    required: true
+    default: "feature/{name}"
+    description: "Working branch for this spec"
+
+  initial_workflow_domain:
+    type: enum
+    required: false
+    values: [milestone, investigation, optimization, refactor, documentation, triage]
+    default: milestone
+    description: "Records which workflow domain was used during ideation, enables downstream flows to load correct config"
+
+body:
+  description: "Markdown document capturing the spec vision"
+  sections:
+    - name: "Motivation"
+      required: true
+      description: "Why this spec matters. User goals and pain points."
+
+    - name: "Goals"
+      required: true
+      description: "What success looks like. Concrete outcomes."
+
+    - name: "Non-Goals"
+      required: false
+      description: "Explicit scope boundaries. What we're NOT doing."
+
+    - name: "Open Questions"
+      required: false
+      description: "Uncertainties to resolve during ideation/planning."
+
+    - name: "Technical Considerations"
+      required: false
+      description: "Known constraints, dependencies, risks."

package/.allhands/schemas/validation-suite.yaml

@@ -0,0 +1,49 @@
+# Validation Suite Schema
+# Files in .allhands/validation/*.md
+# Single source of truth for validation tooling documentation
+
+frontmatter:
+  name:
+    type: string
+    required: true
+    description: "Unique suite identifier (matches filename without .md)"
+
+  description:
+    type: string
+    required: true
+    description: "Use case description - when/why to use this suite for validation"
+
+  globs:
+    type: array
+    items: string
+    required: true
+    description: "File patterns this suite validates (used for discovery and future hooks)"
+
+  tools:
+    type: array
+    items: string
+    required: true
+    description: "CLI tools and packages used by this validation suite (e.g., agent-browser, playwright, axe-core)"
+
+body:
+  description: "Validation tooling usage guide — two-dimensional (stochastic + deterministic) validation playbook"
+  sections:
+    - name: "Purpose"
+      required: true
+      description: "What quality aspects this suite validates (stability, performance, UX, accessibility, etc.)"
+
+    - name: "Tooling"
+      required: true
+      description: "Tools used by this suite, installation instructions, and configuration"
+
+    - name: "Stochastic Validation"
+      required: true
+      description: "Agent-driven exploratory validation playbook. Exploratory patterns, edge case probing strategies, and escape hatches for death spirals (max retries, fallback patterns, when to stop and report)"
+
+    - name: "Deterministic Integration"
+      required: true
+      description: "CI-gated scripted validation. Test scripts, CI configuration, success/failure criteria, and artifact capture"
+
+    - name: "ENV Configuration"
+      required: false
+      description: "Environment variables and configuration needed for both dimensions. Only present when the suite requires external configuration (base URLs, credentials, providers)"

package/.allhands/schemas/workflow.yaml

@@ -0,0 +1,51 @@
+# Workflow Domain Config Schema
+# Single source of truth for workflow domain configuration files in .allhands/workflows/
+
+frontmatter:
+  name:
+    type: string
+    required: true
+    description: "Domain identifier matching spec type values (milestone, investigation, etc.)"
+
+  type:
+    type: enum
+    required: true
+    values: [milestone, investigation, optimization, refactor, documentation, triage]
+    description: "Workflow domain type"
+
+  planning_depth:
+    type: enum
+    required: true
+    values: [deep, focused]
+    description: "Planning depth — milestone uses deep (full research + jury), all others use focused"
+
+  jury_required:
+    type: boolean
+    required: true
+    description: "Whether spec planning activates the 4-member jury review"
+
+  max_tangential_hypotheses:
+    type: integer
+    required: true
+    description: "Cap on tangential emergence hypotheses after core consolidation"
+
+  required_ideation_questions:
+    type: array
+    items: string
+    required: true
+    description: "Questions the ideation scoping flow MUST ask for this domain"
+
+body:
+  description: "Markdown document with domain-specific knowledge and guidance"
+  sections:
+    - name: "Domain Knowledge"
+      required: true
+      description: "Freetext domain-specific considerations, vocabulary, deep dives, gap detection patterns, completeness criteria"
+
+    - name: "Ideation Guidance"
+      required: true
+      description: "How the ideation flow should interpret this domain's knowledge (probe guidance, output sections, principle citations)"
+
+    - name: "Planning Considerations"
+      required: true
+      description: "Constraints, limitations, edge cases for spec planning to surface"

package/.allhands/settings.json

@@ -0,0 +1,57 @@
+{
+  "$schema": "./harness/src/schemas/settings.schema.json",
+  "daemon": {
+    "enabled": true
+  },
+  "git": {
+    "baseBranch": "main"
+  },
+  "emergent": {
+    "hypothesisDomains": [
+      "testing",
+      "stability",
+      "performance",
+      "feature",
+      "ui/ux",
+      "integration"
+    ]
+  },
+  "validation": {
+    "format": {
+      "enabled": false,
+      "command": "pnpm format",
+      "patterns": []
+    }
+  },
+  "tldr": {
+    "enableForHarness": true
+  },
+  "knowledge": {
+    "similarityThreshold": 0.65,
+    "fullContextSimilarityThreshold": 0.82,
+    "contextTokenLimit": 5000
+  },
+  "oracle": {
+    "defaultProvider": "openai",
+    "compactionProvider": "gemini"
+  },
+  "opencodeSdk": {
+    "model": "opencode/gpt-5-nano",
+    "codesearchToolBudget": 12
+  },
+  "spawn": {
+    "promptScopedAutocompactAt": 65
+  },
+  "eventLoop": {
+    "tickIntervalMs": 5000
+  },
+  "prReview": {
+    "reviewMatchPattern": "greptile-apps",
+    "rerunComment": "@greptileai",
+    "checkFrequency": 3
+  },
+  "disabledHooks": [
+    "context signature",
+    "context search-router"
+  ]
+}

package/.allhands/skills/claude-code-patterns/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: claude-code-patterns
+description: Must use when building agents, skills, hooks, commands, or Claude Code tool configs. Contains Claude Code native feature documentation and structure patterns that are essential context.
+globs:
+  - ".allhands/**/*.ts"
+  - ".allhands/**/*.md"
+  - "**/CLAUDE.md"
+  - ".claude/**/*"
+---
+
+<objective>
+Reference for Claude Code native features. Docs auto-sync to `~/.claude-code-docs/docs/`. Read local docs for authoritative reference matching task use case.
+</objective>
+
+<quick_start>
+1. Identify what you're building (skill, agent, hook, etc.)
+2. MUST Read corresponding docs from `~/.claude-code-docs/docs/`
+3. Apply patterns from doc categories below
+</quick_start>
+
+<success_criteria>
+- Correct doc file(s) consulted for task type
+- Implementation follows official patterns
+- Structure matches documented conventions
+</success_criteria>
+
+<workflow>
+### Doc Selection by Task
+
+| Building | Read These (in ~/.claude-code-docs/docs/) |
+|----------|------------------------------------------|
+| Skills | skills.md, plugins.md |
+| Agents/Sub-agents | sub-agents.md |
+| Hooks | hooks-guide.md, hooks.md |
+| MCP/Tools | mcp.md, third-party-integrations.md |
+| Memory/Context | memory.md, settings.md |
+| CLI Commands | cli-reference.md, slash-commands.md |
+| Enterprise/Auth | amazon-bedrock.md, google-vertex-ai.md, iam.md, security.md |
+| IDE Integration | vs-code.md, jetbrains.md, devcontainer.md |
+| CI/CD | github-actions.md, gitlab-ci-cd.md, headless.md |
+
+### Doc Categories
+
+**Core (curator priority)**: skills.md, sub-agents.md, hooks-guide.md, hooks.md, mcp.md, memory.md, plugins.md
+
+**Config**: settings.md, model-config.md, network-config.md, terminal-config.md, output-styles.md
+
+**IDE**: vs-code.md, jetbrains.md, devcontainer.md, desktop.md
+
+**Enterprise**: amazon-bedrock.md, google-vertex-ai.md, microsoft-foundry.md, iam.md, security.md, llm-gateway.md
+
+**CI/CD**: github-actions.md, gitlab-ci-cd.md, headless.md
+
+**Reference**: cli-reference.md, common-workflows.md, troubleshooting.md, changelog.md, quickstart.md
+</workflow>
+
+<examples>
+### Extended Patterns (./docs/)
+- `docs/context-hygiene.md` - CLAUDE.md priority rules, poison context detection
+</examples>

package/.allhands/skills/claude-code-patterns/docs/context-hygiene.md

@@ -0,0 +1,19 @@
+# Context Hygiene Patterns
+
+Read this when: building/modifying CLAUDE.md, debugging inconsistent agent behavior, designing multi-step workflows.
+
+## CLAUDE.md Priority Rules
+
+- CLAUDE.md = system rules (immutable, followed sequentially)
+- User prompts = requests within rules (flexible, optimized)
+- Front-load critical context in CLAUDE.md over dynamic file reads
+- Markdown structure prevents instruction bleed
+
+## Poison Context Detection
+
+Signs context is poisoned:
+- Agent pairs unrelated actions unexpectedly
+- Old instructions persist when they shouldn't
+- Competing rules cause inconsistent behavior
+
+Fix: `/clear` or new session. Prevent: explicit task boundaries, avoid action pairing.