onboard

Interviews stakeholders and writes a project constitution file for feature specifications.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill onboard-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/handarbeit/fabrik/tree/main/plugin/entwurf/skills/onboard
Command: npx skills add https://github.com/handarbeit/fabrik --skill onboard-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a software project without a shared record of goals, scope boundaries, constraints, and vocabulary causes every later feature specification to re-litigate the same questions. This Skill conducts a structured interview with a product owner or domain expert and writes the result as a project constitution at .specify/memory/constitution.md that every downstream spec inherits. ## Core Features & Use Cases - Seven-topic guided interview: Covers the problem, users, success criteria, out-of-scope items, hard constraints, domain vocabulary, and governing principles, in an order where each topic builds on the last. - Non-technical questioning: Translates jargon (accessibility, data residency, integrations) into questions a business operator can answer from their own experience. - Constitution document generation: Writes a versioned constitution with fixed sections (Purpose, Core Principles, Product Context, Scope & Constraints, Technical notes, Governance) and supports amendment mode when one already exists. - Use Case: A restaurant group wants software for tracking kitchen waste. The Skill interviews the operations manager for 30-45 minutes, captures constraints like "must work with no network in the kitchen", records the glossary, and saves a constitution that all future feature specs inherit. ## Quick Start Ask the AI to onboard your project and capture its goals, scope, and ground rules as a constitution before any features are specified.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I create a project constitution before writing feature specs?

Run the onboarding interview, which walks through seven topics: the problem, users, success criteria, out-of-scope items, constraints, vocabulary, and principles. The result is written to .specify/memory/constitution.md and inherited by every later feature specification.

What questions should I ask a non-technical stakeholder about software requirements?

Ask questions they can answer from running their own operation, not technical jargon. For example, ask "is there anything you'd be uncomfortable with being stored abroad?" instead of asking about data residency requirements.

Can I update an existing project constitution instead of starting over?

Yes. If .specify/memory/constitution.md already exists, the interview runs in amendment mode: it shows what is currently recorded, asks what changed, bumps the version, and updates the amendment date rather than rewriting from scratch.

What happens if no folder is connected when writing the constitution?

The Skill does not write to a temporary or scratch directory, since that would silently discard the interview. It tells you upfront that no durable folder is available and hands the finished document back for download instead.

When should a project constitution be revisited?

Revisit it whenever the project's goals or boundaries genuinely shift. A specification that conflicts with the constitution is wrong by default, so the constitution should be amended first rather than making exceptions in individual specs.