pmai-init-project

Initializes product context spine files and routes projects into proposal or design workflows.

4|Updated May 26, 2026
One-click install
npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-init-project-yyg501
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pmai-init-project
Source: https://github.com/YYG501/PM-AI-Harness/tree/main/skills/init-project
Command: npx skills add https://github.com/YYG501/PM-AI-Harness --skill pmai-init-project-yyg501

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new product project with an AI assistant often means scattered context, premature tech-stack decisions, and no durable record of product direction. This Skill establishes a consistent product context spine (PRODUCT.md, PRODUCT-STATE.md, DESIGN.md, PRODUCT-RULES.md, TODO.md) so every later step in the PM workflow builds on recorded facts instead of re-asked questions. ## Core Features & Use Cases - Four-way project classification: Detects whether a target directory is a brand-new project, a documents-only folder, an existing codebase, or an already-onboarded PMAI project, and applies the correct path for each. - Context spine creation: Runs init-project.sh to generate root product documents, docs/ structure, host configuration (AGENTS.md, CLAUDE.md, hooks), and an initial git commit without deciding project type, framework, or scaffolding. - Intake manifest and baseline verification: For existing material, captures SHA-256 hashes of pre-existing files before any writes, then verifies six product-baseline questions against that evidence before allowing a direct jump to design. - Use Case: A solo PM points the assistant at a folder of PRDs and research notes; the Skill fixes an intake manifest, builds the product spine, verifies the documents form an equivalent baseline with PM confirmation, and routes to /pmai-design or /pmai-proposal accordingly. ## Quick Start Initialize this directory as a new PMAI product project and set up the product context files for my app idea.

Frequently Asked Questions about pmai-init-project

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

FAQPage Schema
How do I initialize a new product project with an AI assistant?▼

Run the init-project entry with a project name, target directory, and one-sentence background. It creates PRODUCT.md, PRODUCT-STATE.md, DESIGN.md, PRODUCT-RULES.md, TODO.md, a docs/ structure, and host configuration, then routes you to the proposal step.

How do I onboard an existing codebase into a PM workflow?▼

Point the initializer at the repository. It first captures an intake manifest of file hashes, runs a read-only codebase audit into docs/CODEBASE-AUDIT.md, adds missing product spine files, and never overwrites existing code or creates empty prototype folders.

Can I skip the proposal step if I already have PRDs and documents?▼

Yes, but only after verification. The Skill hashes pre-existing documents into an intake manifest, checks six product-baseline questions against that evidence, and requires explicit PM confirmation plus an equivalent_baseline machine status before routing directly to design.

Does project initialization require gstack, Playwright, or a frontend scaffold?▼

No. Initialization is fully independent of gstack, browsers, Playwright, dev servers, and frontend scaffolding. Browser capability only becomes relevant later during build acceptance for web projects.

What happens if I run initialization on an already onboarded project?▼

It stops without overwriting anything and directs you to the status command to recover context. Re-running initialization on an onboarded project is blocked by design.

Why does initialization not create project.yml or choose a tech stack?▼

By design, initialization only builds the product context spine. Project type, tech stack, and framework are decided when the first design is finalized, at which point .pm-workflow/project.yml is generated.