begin

Automate Towline project setup with discovery, planning, and roadmap artifacts.

Updated Aug 23, 2026

Search Tags:#planning #research #requirements #roadmap #orchestration #project-init #towline

Ready to run

npx skills add https://github.com/SienkLogic/towline --skill begin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: begin
Source: https://github.com/SienkLogic/towline/tree/main/plugins/dev/skills/begin
Command: npx skills add https://github.com/SienkLogic/towline --skill begin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Towline project initialization can be complex and error-prone. This skill guides deep discovery, coordinates research and planning, and creates a structured roadmap while keeping your main context lean by delegating heavy tasks to subagents.

Core Features & Use Cases

Orchestrates end-to-end project setup: questioning, research planning, requirements scoping, and roadmap generation.
Generates planning artifacts in .planning (REQUIREMENTS.md, ROADMAP.md, PROJECT.md, STATE.md, CONTEXT.md, etc.) and manages a phased roadmap.
Delegates heavy work to subagents and summarizes outputs to minimize context usage while ensuring traceability.

Quick Start

Provide your project vision and constraints, and let /dev:begin orchestrate questioning, research, requirements, and roadmap.

Frequently Asked Questions about begin

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

FAQPage Schema

How do I automate project initialization from concept to roadmap?▼

Project initialization from concept to roadmap is automated by orchestrating deep discovery questioning, delegating research to subagents, and scoping requirements to generate structured planning artifacts like REQUIREMENTS.md and ROADMAP.md.

How do I plan requirements without bloating my main context window?▼

Requirements planning prevents main context bloat by delegating heavy research and scoping tasks to subagents, then summarizing their outputs to maintain traceability while keeping the primary workspace lean.

What planning artifacts are generated during project setup?▼

Project setup generates planning artifacts within a .planning directory, including REQUIREMENTS.md, ROADMAP.md, PROJECT.md, STATE.md, and CONTEXT.md to enforce disciplined state management and document decisions.

Can I configure workflow preferences for project orchestration?▼

Workflow preferences for project orchestration are configurable, allowing you to customize the phased roadmap creation, research planning, and requirement scoping steps according to your specific project vision and constraints.

What's the best way to scope requirements for a new project vision?▼

Scoping requirements for a new project vision is best handled through guided deep discovery, where initial questioning feeds into automated research planning and phased roadmap generation to safely handle findings.

Why does my project planning workflow need state management?▼

Project planning workflows need state management to enforce disciplined tracking of decisions, safely handle research findings, and maintain structured progress across phased roadmap steps without losing context.