rai-project-create

Automating greenfield project onboarding involves collecting project identity, requirements, constraints, and architecture context to populate governance templates. This skill guides you through that data gathering and generates the full governance suite automatically.

A greenfield software project typically requires a vision document, PRD, guardrails, backlog, system context, and system design. Generating these six governance documents ensures proper project alignment, architecture tracking, and rule enforcement from the start.

Creating a governance knowledge graph involves mapping project identity, requirements, and architecture context into structured nodes. This skill builds a 30+ node knowledge graph to support ongoing governance tracking and future development sessions.

Yes, you can reuse an idempotent workflow across multiple new projects. This approach ensures parser-ready outputs and enforces governance gates consistently, allowing you to safely regenerate the governance suite without duplicating data.

Yes, you need to run project initialization first. This skill targets the phase immediately after initialization, using the established environment to generate the full governance suite and populate the knowledge graph.

The best way to enforce governance gates during greenfield setup is by using an automated template generation workflow. This ensures parser-ready outputs and structural compliance, preventing manual errors when defining system design and guardrails.