init_harness

Create a standardized thoughts directory structure for Gemini CLI repositories.

20|6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/adrielp/ai-engineering-harness --skill init-harness-adrielp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init_harness
Source: https://github.com/adrielp/ai-engineering-harness/tree/main/gemini/skills/init_harness
Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill init-harness-adrielp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repository bootstrap for Gemini context by creating a standardized thoughts/ directory structure and an initial ticket template.

Core Features & Use Cases

  • Create thoughts/shared with tickets, plans, and research
  • Create thoughts/global for cross-repo concerns
  • Add a ready-to-use ticket template at thoughts/shared/tickets/ticket-template.md
  • Optionally create a personal thoughts directory under thoughts/$(whoami)/{tickets,plans,research}

Quick Start

Run the init_harness command in your repository to create the thoughts directory structure for Gemini context.

Frequently Asked Questions about init_harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap Gemini context scaffolding in an existing repository?

To bootstrap Gemini context scaffolding, run the init_harness command in your repository. It creates a standardized thoughts directory with shared, global, and ticket template structures for immediate Gemini CLI context.

What directory structure is needed for Gemini CLI context engineering?

Gemini CLI context engineering uses a thoughts directory containing shared areas for tickets, plans, and research, a global area for cross-repo concerns, and an optional personal directory for individual context.

Can I set up a personal thoughts directory for Gemini context alongside shared areas?

Yes, you can optionally create a personal thoughts directory under thoughts/$(whoami). It validates and structures personal tickets, plans, and research separately from the shared and global context areas.

Does the repository bootstrap process include a ticket template for Gemini thoughts?

Yes, the repository bootstrap process places a ready-to-use ticket template at thoughts/shared/tickets/ticket-template.md. This ensures standardized ticket formatting within the Gemini context scaffold.

When should I use an automated context scaffold instead of manual directory setup for Gemini?

Use an automated context scaffold when initializing new or existing repositories for the Gemini CLI. It eliminates manual directory creation errors and instantly validates your standardized thoughts structure.