- Home
- Skills
- Yellinzero
- Aico
- Aico Pm Init
aico-pm-init_skill
- TypeScript
0
GitHub Stars
2
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill yellinzero/aico --skill aico-pm-init- constitution.template.md2.9 KB
- SKILL.md2.1 KB
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
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.