playbooks

home / skills / yellinzero / aico / aico-pm-init

aico-pm-init skill

/.codex/skills/aico-pm-init

This skill initializes the PM constitution by guiding you through setup questions and generating the project document.

npx playbooks add skill yellinzero/aico --skill aico-pm-init

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.1 KB
---
name: aico-pm-init
description: |
  Initialize PM environment by creating constitution document from template.

  Use this skill when:
  - Running /pm.init command
  - User asks to "initialize PM", "setup product management", "create constitution"
  - Starting a new project and need to establish product constraints and domain info
  - Need to create docs/reference/pm/constitution.md for a new project
---

# PM Init

Initialize the product constitution document that provides shared constraints and domain information for all PM activities.

## Language Configuration

Before generating any content, check `aico.json` in project root for `language` field to determine the output language. If not set, default to English.

## Process

1. **Check existing**: Look for `docs/reference/pm/constitution.md`
2. **If exists**: Ask user if they want to overwrite or update specific sections
3. **If not exists**:
   - Read template from `references/constitution.template.md`
   - Guide user through questions to fill template
4. **Save output**: Write to `docs/reference/pm/constitution.md`

## Document Header Format

All generated documents MUST use this unified header format:

```markdown
# [Document Title]

> Project: [project-name]
> Created: YYYY-MM-DD
> Last Updated: YYYY-MM-DD
```

## Guided Questions

Ask user about:

| Section          | Questions                                                  |
| ---------------- | ---------------------------------------------------------- |
| Product Overview | Product name? One-line description? Target users?          |
| Domain Info      | Industry/market? Key terminology? Compliance requirements? |
| Constraints      | Technical stack? Business constraints?                     |
| Standards        | Documentation language? Naming conventions?                |

## Template

See `references/constitution.template.md` for the full constitution template.

## Output

```
✓ Created docs/reference/pm/constitution.md
✓ PM environment initialized
```

## Key Rules

- ALWAYS use the unified header format
- MUST guide user through key questions before generating
- ALWAYS save to `docs/reference/pm/constitution.md`

Overview

This skill initializes a product management (PM) environment by creating a constitution document from a template. It guides the user through targeted questions, enforces a unified header format, and writes the finalized constitution to docs/reference/pm/constitution.md. Use it to establish shared product constraints, domain details, and documentation standards at project start.

How this skill works

The skill first checks whether docs/reference/pm/constitution.md already exists and prompts to overwrite or update specific sections if found. If not present, it loads the constitution template, asks guided questions for each section (product overview, domain info, constraints, standards), fills the template, applies the required document header format, and saves the file. It confirms successful creation and that the PM environment is initialized.

When to use it

  • Starting a new project and establishing product constraints and domain context
  • Running the /pm.init command or asking to initialize PM or create a constitution
  • Setting up consistent documentation and naming or language standards for PM work
  • You need a canonical docs/reference/pm/constitution.md for onboarding and alignment

Best practices

  • Always answer guided questions with concise, decision-focused responses to produce actionable content
  • Verify the project name and target users early to keep the constitution aligned with stakeholders
  • Preserve the unified header format exactly (title, Project, Created, Last Updated) on every generated document
  • When a constitution exists, prefer targeted updates instead of full overwrites to retain historical context
  • Record compliance and technical constraints clearly to guide future product decisions

Example use cases

  • A product lead starts a new repo and needs a single-source PM constitution for the team
  • Onboarding a new PM who needs a concise summary of domain, constraints, and standards
  • Aligning engineering and design around documented technical and business constraints
  • Refreshing documentation language and naming conventions across product artifacts

FAQ

What happens if a constitution already exists?

The skill asks whether to overwrite the whole file or update specific sections, preserving or replacing content based on your choice.

Is the document header mandatory?

Yes. The skill always applies the unified header format with project name and created/last-updated dates.

Can I change the output language?

The skill checks aico.json for a language setting and defaults to English if none is set.