initialize-project

Name: initialize-project
Availability: InStock
Author: 0xobat

Create project harness files including init.sh, verify.sh, features.json, and progress.txt.

Updated Feb 22, 2026

Search Tags:#workflow #devops #project setup #initialization #bootstrap #harness

Ready to run

npx skills add https://github.com/0xobat/claude-skills --skill initialize-project-0xobat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: initialize-project
Source: https://github.com/0xobat/claude-skills/tree/main/dev/skills/initialize-project
Command: npx skills add https://github.com/0xobat/claude-skills --skill initialize-project-0xobat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the setup of a new project's foundational structure, ensuring all necessary harness components are present and correctly configured from the start.

Core Features & Use Cases

Mandatory Harness Components: Guarantees the creation of init.sh, verify.sh, features.json, and progress.txt.
Granular Feature Definition: Enforces detailed feature breakdown in features.json to prevent scope creep and enable incremental development.
Idempotent Setup: Ensures init.sh can be run multiple times without adverse effects.
Real Verification: Requires verify.sh to include actual checks (tests, linters) from day one.
Session Handoff: Establishes progress.txt for seamless continuation of work between sessions.

Quick Start

Use the initialize-project skill to bootstrap a new project with the required harness structure.

Frequently Asked Questions about initialize-project

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

FAQPage Schema

How do I bootstrap a new project to prevent scope creep and context loss?▼

To bootstrap a new project without context loss, you need a structured harness with idempotent setup scripts, granular feature definitions, and session logging. This enforces best practices by creating specific configuration files that track incremental development and progress.

What is a project harness and why do I need it for initialization?▼

A project harness is a mandatory foundational structure created during initialization to prevent quality decay. It includes idempotent setup scripts, granular feature definitions, and session logging to ensure necessary components are correctly configured from the start.

How do I set up idempotent setup scripts and real verification for my devops workflow?▼

You set up idempotent setup scripts and real verification by creating specific harness files like init.sh and verify.sh. The init.sh script must be runnable multiple times without adverse effects, while verify.sh includes actual checks like tests and linters from day one.

How does session handoff work when initializing a project with a harness?▼

Session handoff during project initialization works by establishing a progress.txt file for seamless continuation of work between sessions. This mandatory harness component logs your current state, preventing context loss when you resume development.

Can I use this project initialization approach for incremental development across multiple sessions?▼

Yes, you can use this initialization approach for incremental development across multiple sessions. It enforces detailed feature breakdown in a features.json file to prevent scope creep and uses a progress.txt file to enable seamless session handoff.

What limitations exist when enforcing a mandatory harness structure for project setup?▼

The limitation of enforcing a mandatory harness structure is that it requires strict adherence to specific file formats and content guidelines for init.sh, verify.sh, features.json, and progress.txt, which may restrict unconventional project setups.