constitution-creation ยท diff

git:20260507.9f5be95 to git:20260601.da7723a

29 added, 29 removed. Audit A to A.

- ---
- name: constitution-creation
- description: Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.
- allowed-tools: Read, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion
+ ---
+ name: constitution-creation
+ description: Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.
+ allowed-tools: Read, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion
graph:
domains: [domain:software-engineering]
skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
workflows: [workflow:feature-development]
topics: [topic:developer-experience]
roles: [role:tech-lead, role:backend-engineer]
---
- - Formalizing existing project standards into a constitution
- - Updating governance principles for an evolving project
- - Before writing specifications for a new feature area
-
- ## Distinction from Specification
-
- - **Constitution**: Defines project-wide governance (HOW the project operates)
- - **Specification**: Defines feature-level requirements (WHAT to build)
-
- ## Process
-
- 1. **Gather context** - Assess project type, audience, compliance needs, existing standards
- 2. **Define dev guidelines** - Coding standards, branching strategy, review process
- 3. **Set code quality standards** - Linting, formatting, complexity limits, naming conventions
- 4. **Establish testing policies** - Coverage thresholds, test types, CI requirements
- 5. **Specify UX requirements** - Accessibility, responsiveness, performance budgets
- 6. **Define performance benchmarks** - Load times, throughput, memory limits
- 7. **Establish security constraints** - Auth, data handling, vulnerability policies
- 8. **Document architecture principles** - Modularity, dependencies, extensibility
- 9. **Human review** - Approve constitution before proceeding
-
- ## Tool Use
-
- Invoke via babysitter process: `methodologies/spec-kit/spec-kit-specification` (constitution phase)
- Full pipeline: `methodologies/spec-kit/spec-kit-orchestrator`
+ - Formalizing existing project standards into a constitution
+ - Updating governance principles for an evolving project
+ - Before writing specifications for a new feature area
+
+ ## Distinction from Specification
+
+ - **Constitution**: Defines project-wide governance (HOW the project operates)
+ - **Specification**: Defines feature-level requirements (WHAT to build)
+
+ ## Process
+
+ 1. **Gather context** - Assess project type, audience, compliance needs, existing standards
+ 2. **Define dev guidelines** - Coding standards, branching strategy, review process
+ 3. **Set code quality standards** - Linting, formatting, complexity limits, naming conventions
+ 4. **Establish testing policies** - Coverage thresholds, test types, CI requirements
+ 5. **Specify UX requirements** - Accessibility, responsiveness, performance budgets
+ 6. **Define performance benchmarks** - Load times, throughput, memory limits
+ 7. **Establish security constraints** - Auth, data handling, vulnerability policies
+ 8. **Document architecture principles** - Modularity, dependencies, extensibility
+ 9. **Human review** - Approve constitution before proceeding
+
+ ## Tool Use
+
+ Invoke via babysitter process: `methodologies/spec-kit/spec-kit-specification` (constitution phase)
+ Full pipeline: `methodologies/spec-kit/spec-kit-orchestrator`