up-inception

Articulate project vision and scope with use cases and non-functional requirements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/js-rom/Luis --skill up-inception
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: up-inception
Source: https://github.com/js-rom/Luis/tree/main/.agents/skills/up-inception
Command: npx skills add https://github.com/js-rom/Luis --skill up-inception

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align stakeholders by articulating a shared vision and justified scope for the inception phase of a potential new system.

Core Features & Use Cases

  • Define the project vision and boundaries to guide decision making during early exploration.
  • Identify representative use cases and critical non-functional requirements to form a business case for further investment.
  • Produce initial artifacts that can be refined in subsequent elaboration phases.

Quick Start

Provide a brief, first-draft vision and scope for a project and outline the initial use cases and essential non-functional considerations.

Frequently Asked Questions about up-inception

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

FAQPage Schema
What is project inception and when do I need to define a shared vision?

Project inception is the initial phase where you articulate a shared vision and justified scope to align stakeholders. You need it during early exploration of a potential new system to guide decision making and decide whether deeper investment is warranted.

How do I align stakeholders and define project boundaries during inception?

Align stakeholders by articulating a shared vision and analyzing representative use cases alongside critical non-functional requirements. This process defines project boundaries and forms a business case to justify further exploration and investment.

What's the best way to build a business case for a new system?

Build a business case for a new system by identifying representative use cases and essential non-functional requirements. Analyzing these elements during inception justifies further investment and determines whether deeper exploration is warranted.

Can I use non-functional requirements to decide if a project warrants deeper exploration?

Critical non-functional requirements are analyzed alongside representative use cases to decide whether deeper exploration is warranted. Specifying these constraints helps form a justified business case and establishes project boundaries during the inception phase.

How do I capture constraints and architectural directions as initial artifacts?

Capture constraints, risks, and architectural directions as initial artifacts by analyzing use cases and non-functional requirements during inception. These artifacts guide future elaboration phases and document the agreed project scope.

What do I need to provide to start defining project vision and scope?

Provide a brief, first-draft vision and scope for a project, then outline the initial use cases and essential non-functional considerations. This input allows the inception process to align stakeholders and produce initial artifacts for refinement.