skills.rest
jeremy-newhouse
jeremy-newhouseCOMMUNITY
Explore all skills by this author →
GitHub

wa:start-project

Plan and register an end-to-end project kickoff with tech stack, architecture, documentation, and feature backlog.

Updated Mar 26, 2026
Search Tags:#documentation generation#architecture planning#project kickoff#tech stack selection#lifecycle backlog#plugin preflight#tracker integration
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-start-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wa:start-project
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/start-project
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-start-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a new project often stalls at the requirements and documentation stage, where the team needs clear tech-stack choices, architecture direction, and an agreed feature plan before writing code.

Core Features & Use Cases

  • Tech stack and architecture kickoff: Collects vision, selects a stack, and coordinates architecture validation through dedicated architect agents.
  • Project documentation & standards setup: Pulls the latest evolv-coder standards, syncs context, and creates BRD/PRD/ADRs/feature docs based on project level and doc platform.
  • Lifecycle feature backlog registration: Turns the interview outcomes into an approved backlog and optionally creates tracker issues.

Quick Start

Run the wa:start-project skill after your project has been scaffolded by /eck:new-project, then follow the interview prompts to produce the tech stack, docs, and an initial feature backlog.

Frequently Asked Questions about wa:start-project

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

FAQPage Schema
How do I plan tech stack selection and architecture for a new project kickoff?▼

Project kickoff documentation is generated by pulling the latest evolv-coder standards, syncing context, and creating BRD, PRD, ADRs, and feature docs based on your project level and documentation platform.

Can I automatically create tracker issues from my feature backlog?▼

Yes, you can create tracker issues from your feature backlog. During final lifecycle registration, the Skill turns interview outcomes into an approved backlog and optionally creates tracker issues for your project.

Do I need to scaffold my project before running the project kickoff process?▼

Yes, you need to scaffold your project first. You should run this kickoff process after your project has been scaffolded by /eck:new-project to ensure project constants and settings are filled before development begins.

What are the limitations of using an interview-driven project kickoff approach?▼

A limitation of the interview-driven project kickoff approach is that it requires plan-mode and enforced preflight plugin checks, meaning you cannot bypass the staged requirement gathering or skip syncing standards and context before development.

Related Skills

Explore More Software Engineering Skills→
lubusINlubusIN
48

frappe-project-triage

Identify Frappe project type, installed apps, version, and tooling.

Official
Intermediate
ldilovldilov
3

speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues.

Community
Advanced
DavidEdeniDavidEdeni
1

documentation-and-adrs

Record ADRs and architecture notes with templates and inline documentation.

Community
Intermediate
vladm3105vladm3105
16

doc-brd

Create Layer 1 BRD artifacts defining business needs and strategic objectives.

Community
Advanced