sdd-create-constitution

Generate mission, tech-stack, and roadmap files from repository evidence.

21|5|Updated May 21, 2026
One-click install
npx skills add https://github.com/jentic/jentic-api-scorecard --skill sdd-create-constitution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-create-constitution
Source: https://github.com/jentic/jentic-api-scorecard/tree/main/.claude/skills/sdd-create-constitution
Command: npx skills add https://github.com/jentic/jentic-api-scorecard --skill sdd-create-constitution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of a Spec-Driven Development (SDD) constitution from current repository evidence, ensuring that the project foundation aligns with reality.

Core Features & Use Cases

  • Bootstrap Constitution: Automatically generates mission.md, tech-stack.md, and roadmap.md files based on repository evidence.
  • Existence Guard: Checks for existing constitution files and prompts for overwrite confirmation if necessary.
  • Parallel Research: Conducts thorough research across code trees, documentation, and configuration files.
  • Synthesis: Combines research findings into a coherent constitution, distinguishing between confirmed facts, inferred conclusions, and unknowns.
  • User Confirmation: Issues a single AskUserQuestion call for user input before writing files.
  • File Writing: Edits files in place and stops, leaving branch, commit, and PR creation to user actions.

Quick Start

Run the skill to bootstrap your constitution: /sdd-create-constitution

Frequently Asked Questions about sdd-create-constitution

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

FAQPage Schema
How do I bootstrap a spec-driven development constitution from existing repository evidence?

To bootstrap a spec-driven development constitution, this skill conducts parallel research across your code, documentation, and configuration files, synthesizing findings, and writes mission.md, tech-stack.md, and roadmap.md files after user confirmation.

What is a spec-driven development constitution and why do I need one?

A spec-driven development constitution establishes a project foundation aligning with repository reality. It consists of mission.md, tech-stack.md, and roadmap.md files that define project scope, technology stack, and future development milestones.

Can I generate constitution files automatically without manually writing documentation?

Yes, you can generate constitution files automatically. The skill analyzes repository evidence, distinguishes between confirmed facts and inferred conclusions, and prompts for a single user confirmation before writing the foundation files.

Does the constitution bootstrap process overwrite existing mission and tech stack files?

The skill includes an existence guard that checks for existing constitution files. If mission.md, tech-stack.md, or roadmap.md already exist, it prompts for overwrite confirmation before replacing them.

Will the skill automatically commit constitution files or create a pull request?

No, the skill edits files in place and stops. It leaves branch creation, commit operations, and pull request generation entirely to user actions after the constitution files are written.

How does code analysis handle unknown or missing information when synthesizing the project foundation?

During synthesis, the code analysis explicitly distinguishes between confirmed facts derived from repository evidence, inferred conclusions, and unknowns, ensuring the generated constitution reflects actual project state without guessing.