project-init

Initialize ARCHITECTURE.md and a deterministic lockfile for reproducible builds.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/iago-leal/skills --skill project-init-iago-leal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-init
Source: https://github.com/iago-leal/skills/tree/main/mdcu-framework/project-init
Command: npx skills add https://github.com/iago-leal/skills --skill project-init-iago-leal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill formalizes the implicit technical contract of a software project by creating a stable, auditable foundation (ARCHITECTURE.md) and a deterministic lockfile, preventing ad hoc changes that destabilize builds.

Core Features & Use Cases

  • Create ARCHITECTURE.md at the project root detailing stack, conventions, guardrails, and governance.
  • Initialize the chosen package manager and establish a lockfile to ensure reproducible builds across environments.
  • Produce an initial commit that captures ARCHITECTURE.md, the manifest, and the lockfile as the project’s anchor.

Quick Start

Run /project-init to generate the architecture contract and lockfile, then commit the initial project contract.

Frequently Asked Questions about project-init

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

FAQPage Schema
How do I create an ARCHITECTURE.md file to establish project guardrails?

To establish project guardrails, generate an ARCHITECTURE.md file at the project root detailing the technical stack, conventions, and governance to formalize the implicit project contract and prevent ad hoc changes.

Why do I need a deterministic lockfile for reproducible builds?

A deterministic lockfile ensures reproducible builds across environments by locking exact dependency versions. Initializing your chosen package manager with this lockfile prevents unstable updates from destabilizing the build process.

What is the best way to initialize a formal technical contract for a software project?

The best way to initialize a formal technical contract is to validate a chosen stack, manifest, and lockfile, then produce an initial commit capturing these artifacts as the project anchor to ensure an auditable foundation.

Do I need a chosen stack and manifest before initializing project architecture?

Yes, you need a chosen stack, manifest, and corresponding lockfile before initialization. The process validates these prerequisites and commits the architecture contract alongside them to enforce reproducible builds.

When should I apply architectural changes to the project contract?

Apply architectural changes during project startup or whenever modifying the technical foundation. Re-running the initialization validates updated stack definitions, package managers, and guardrails, maintaining a stable, auditable contract.

Can I use project-init to enforce specific package managers and stack definitions?

Yes, you can use it to enforce specific package managers and stack definitions. It validates the chosen manifest and lockfile, committing them as artifacts within the MDCU workflow to guarantee reproducible builds.