initialize-project

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.

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.

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.

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.

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.

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.