bootstrap-project-rules

To set up engineering rules, you establish foundational project contracts by generating `docs/ai/ENGINEERING_RULES.md` and task-specific `IMPLEMENTATION_CONTRACT.md` files, updating root `AGENTS.md` and `CLAUDE.md` configurations to define a clear implementation path.

Managing architectural decisions involves classifying choices into 'Locked now', 'Deferred', and 'Banned/Avoid' categories. This decision framework manages dependencies and ensures a consistent starting point for development after the design phase.

You need to create an implementation contract during the post-design, pre-implementation phase. It solidifies the technology stack, defines core architectural boundaries, and sets up the initial documentation structure before any code is written.

Yes, bootstrap-project-rules updates root agent and Claude configuration files (`AGENTS.md`, `CLAUDE.md`) and the project `README.md` with managed sections. This ensures repository contracts are synchronized across your project documentation.

Yes, you need a completed design phase before establishing project rules. This skill automates the critical post-design phase by taking design outputs and converting them into actionable engineering rules and implementation contracts.

Classifying decisions into 'Locked now', 'Deferred', and 'Banned/Avoid' categories prevents scope creep and architectural drift. It manages dependencies by explicitly defining what is finalized, what is postponed, and what approaches to avoid during implementation.