project-initializer

Create initial live and reference state files for agents-stack repositories.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/thompson0012/agents-stack --skill project-initializer-thompson0012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-initializer
Source: https://github.com/thompson0012/agents-stack/tree/main/templates/.agents/skills/using-agents-stack/project-initializer
Command: npx skills add https://github.com/thompson0012/agents-stack --skill project-initializer-thompson0012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a safe, repeatable bootstrap for the durable global state a repository needs to operate truthfully within the agents-stack harness, preventing gaps and fake history.

Core Features & Use Cases

  • Bootstraps the live state files used by the harness, including docs/live/tracked-work.json, docs/live/current-focus.md, docs/live/roadmap.md, docs/live/ideas.md, docs/live/progress.md, docs/live/memory.md.
  • Preserves any existing durable records when present and avoids fabricating backlog or sprint history.
  • Enables a clean starting point for new projects entering the harness or for repositories reinitializing after a reset.

Quick Start

Run the project initializer to create the durable global state in docs/live and docs/reference without fabricating history.

Frequently Asked Questions about project-initializer

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

FAQPage Schema
How do I bootstrap durable repo state for a fresh project harness?▼

Initializing a new agents-stack repository requires creating live state files like docs/live/tracked-work.json and docs/live/current-focus.md to establish a truthful operational baseline without guessing prior history.

What's the best way to initialize live and reference docs without fabricating sprint history?▼

To initialize docs without fabricating history, use a bootstrap tool that preserves existing durable records and writes clean docs/live/progress.md and docs/reference/architecture.md files reflecting only reality.

Which live state files are needed to start tracking work in a new repository?▼

Work tracking requires live state files including docs/live/tracked-work.json, current-focus.md, roadmap.md, ideas.md, progress.md, and memory.md to maintain operational truth within the harness.

Can I reinitialize docs/live and docs/reference after a repository reset?▼

Reinitializing docs/live and docs/reference after a reset is supported, applying the bootstrap to rebuild durable global state while preserving any existing records that remain.

Does the state bootstrap process preserve existing durable records?▼

The state bootstrap preserves existing durable records when present, ensuring valid tracked-work.json and memory.md files are retained rather than overwritten during initialization.