project:vision
Project Vision
Defines the overall system — its purpose, stakeholders, goals, technical constraints, and shared architectural decisions that apply across all specs. This is the starting point for building a large system composed of multiple specifications.
When to use
Use this skill when the user needs to:
- Start a new large-scale project (SaaS, platform, multi-module app)
- Define shared technical decisions before breaking work into specs
- Document system-level goals and constraints that span multiple features
Instructions
Step 1: Gather Information
Use the AskUserQuestion tool to gather:
- Project name — kebab-case identifier (e.g., "my-saas", "trading-platform")
- What is this system? — Brief description of what it does
More from ikatsuba/skills
spec:design
Technical Design - generates architecture diagrams, interfaces, and data flow based on requirements and chosen research solutions. Use when designing how a feature will be built.
18git:amend
Amend Commit - modifies the last commit with staged changes or new message
15spec:requirements
Requirements Analysis - gathers requirements through structured questions and produces a requirements document with testable acceptance criteria. Use when starting a new feature spec or documenting requirements.
14spec:tasks
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
14git:commit
Smart Commit - stages all changes and creates a conventional commit
13spec:do-all
Execute All Tasks - runs all pending tasks from the tasks document, with parallel subtask execution when safe
9