harness-init_skill

This skill initializes a project for harness setup using natural language, delivering ready-to-run plans and defaults for immediate development.
  • Shell

212

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill chachamaru127/claude-code-harness --skill harness-init

  • SKILL.md3.6 KB

Overview

This skill initializes a project to the Harness specification so development can begin with natural language only. It prepares a runnable workspace, generates initial files (Plans.md, AGENTS.md, CLAUDE.md), and performs an environment diagnosis and SSOT initialization. The setup completes with a minimum of one interactive question and yields a ready Plan→Work→Review cycle.

How this skill works

The skill asks a single unified question to capture project intent, audience, and whether to use smart defaults or explicit configuration. It can generate a new project (real scaffolding like create-next-app), introduce the harness into an existing repo by analyzing source code, or apply a specified tech stack such as next + supabase. After generation it runs environment checks, initializes single source of truth files, and returns a completion report with next steps.

When to use it

  • When you type /harness-init to start a new project quickly
  • To introduce the harness into an existing codebase and auto-configure agents
  • When you want immediate defaults and minimal interaction to launch development
  • If you need a reproducible Plan→Work→Review workflow ready to run
  • When specifying stack or mode (e.g., --stack=next-supabase or --mode=solo)

Best practices

  • Prefer the single-question flow for fastest setup; use 'leave it to you' to skip confirmation
  • Specify --stack and --name when you need deterministic scaffolding and repo names
  • Run the skill from the project root so existing files can be analyzed and preserved
  • Review the generated Plans.md and AGENTS.md before running automated work commands
  • Use the optional Codex CLI setup (/setup codex) only if you need Codex compatibility

Example use cases

  • Launch a new Next.js + Supabase app with harness scaffolding using --stack=next-supabase
  • Introduce harness to an existing JavaScript project to enable autonomous Plan→Work→Review cycles
  • Quickly scaffold a solo-mode project with smart defaults by saying 'leave it to you'
  • Initialize SSOT and agent configuration to hand off to automated agents or human developers
  • Prepare a repository for immediate /plan-with-agent and /work commands after setup

FAQ

Typically one unified question; a second confirmation appears only if you opted out of defaults.

Can it analyze an existing project?

Yes. When run from a repo, it inspects code to integrate the harness without overwriting key files.

What stacks are supported by default?

Smart defaults use next-supabase; you can override with --stack or a detailed response.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
harness-init skill by chachamaru127/claude-code-harness | VeilStrat