safe-start

Generate canonical YAML artifacts for new codebase projects.

80|2|Updated May 14, 2026

Search Tags:#workflow #yaml #scopes #project-start #artifact-management #structured-artifacts

Ready to run

npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill safe-start

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: safe-start
Source: https://github.com/PriNova/pi-agent-codebase-workflows/tree/main/skills/safe-start
Command: npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill safe-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured artifact management for new codebases: replaces fragile prose docs with a canonical YAML baseline that enables consistent discovery, validation, and governance.

Core Features & Use Cases

Defines a resolved docs root and standard artifact set (repo-inventory.yaml, project-intent.yaml, architecture.yaml, data-flow.yaml, invariants.yaml, risk-register.yaml, contracts.yaml, adr.yaml, agent-operating-guide.yaml) to standardize project setup.
Enforces stable IDs, ownership rules, upsert semantics, and explicit references to prevent drift across artifacts.
Supports a repeatable, auditable Greenfield workflow that guides teams from intent through scaffold to validation.

Quick Start

Run the safe-start pass to generate the initial canonical artifacts for a new repository, including scope layout and baseline governance artifacts.

Frequently Asked Questions about safe-start

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

FAQPage Schema

How do I create structured YAML artifacts for a new codebase project?▼

Structured YAML artifacts replace fragile prose documentation with canonical files like project-intent.yaml and data-flow.yaml, enabling consistent discovery, validation, and governance while preventing drift through stable IDs and explicit references.

What is the best way to standardize greenfield project setup with structured artifacts?▼

The best way to standardize greenfield project setup is to enforce strict artifact schemas, stable IDs, and upsert semantics. This creates a repeatable, auditable workflow that guides teams from intent through scaffold to validation.

Can I enforce governance rules and ownership tracking using YAML files in a repository?▼

Yes, you can enforce governance rules and ownership tracking using canonical YAML files. The baseline generates artifacts like invariants.yaml and adr.yaml with explicit references and ownership rules to ensure auditable project governance.

Does structured artifact management support strict schemas and upsert semantics for YAML files?▼

Structured artifact management supports strict schemas, stable IDs, and upsert semantics for YAML files. This ensures consistent, auditable baselines and prevents configuration drift across artifacts within the repository.

What are the limitations of using prose documentation for new codebase governance instead of structured YAML?▼

Prose documentation creates fragile baselines that lack strict schemas, stable IDs, and explicit references, leading to configuration drift. Structured YAML artifacts solve this by providing auditable, upsert-enabled governance files.