constitution-generator

Generates a Markdown-ready constitution input for /speckit.constitution from project characteristics.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/aaronbassett/claude-bell --skill constitution-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constitution-generator
Source: https://github.com/aaronbassett/claude-bell/tree/main/.claude/skills/constitution-generator
Command: npx skills add https://github.com/aaronbassett/claude-bell --skill constitution-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate a clear project constitution input for the /speckit.constitution command by guiding structured discovery and translating project characteristics into actionable principles.

Core Features & Use Cases

  • Structured discovery workflow: Four rounds of clarifying questions (project nature, technical profile, risk & operations, and quality expectations) to capture essential context.
  • Principle mapping: Recommends engineering principles and patterns matched to the project profile from the catalog.
  • Output-ready constitution: Produces a Markdown-ready constitution input suitable for /speckit.constitution.

Quick Start

Start constitution-generation for a new internal web app project with a 6-person team, distributed architecture, 12-month lifespan, and continuous delivery.

Frequently Asked Questions about constitution-generator

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

FAQPage Schema
What is a project constitution and how does it help engineering governance?

A project constitution defines core engineering principles and governance standards to guide team decisions. It captures project nature, technical profile, risk operations, and quality expectations, translating them into actionable principles that bootstrap governance for new projects.

How do I bootstrap governance and engineering principles for a new project?

Bootstrapping governance starts with structured discovery across four rounds covering project nature, technical profile, risk and operations, and quality expectations. The process maps your project characteristics to matched principles and outputs a ready-to-use constitution input.

How do I generate a constitution input for the speckit constitution command?

To generate a constitution input, the skill guides you through structured discovery questions about your project profile. It then translates your answers into a matched set of engineering principles, producing a Markdown-ready input formatted for the speckit constitution command.

Do I need an existing project to define engineering principles and a constitution?

No, you do not need an existing project. The constitution generator is designed for starting new projects, bootstrapping governance, and defining engineering standards early. It captures essential context through structured discovery to establish foundational principles.

What's the best way to establish engineering standards for a distributed team?

The best way is to run a structured discovery workflow that captures technical profile, risk, and quality expectations. This translates your team's project characteristics into actionable engineering principles, outputting a constitution input that guides continuous delivery and governance.

Are there limitations to using a generated constitution for project governance?

The generated constitution is limited to the context you provide during the four discovery rounds. It produces a principle set and Markdown input for governance, but the effectiveness depends on accurately representing your project nature, technical profile, risk operations, and quality expectations.