dev-start

Create a feature branch and generate specification documents from an Excel design workbook.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Takas0522/ai-sldc-demo-takas-2603 --skill dev-start-takas0522
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-start
Source: https://github.com/Takas0522/ai-sldc-demo-takas-2603/tree/main/.github/skills/dev-start
Command: npx skills add https://github.com/Takas0522/ai-sldc-demo-takas-2603 --skill dev-start-takas0522

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of starting new feature work by guiding branch creation, generating specification documents from an Excel design sheet, committing the results, and preparing downstream development tasks.

Core Features & Use Cases

  • Feature kickoff flow: confirm the feature name, item number, and Excel design file before work begins.
  • Branch and documentation automation: create a feature branch and generate business and system spec files under docs/specs.
  • Task handoff support: prepare the generated specs for commit, push, and task construction with dev-task-builder.
  • Use case: A team receives a new feature design workbook and wants a consistent repository structure, traceable specs, and ready-to-implement task files.

Quick Start

Use the dev-start skill to begin a new feature by creating the branch, generating the specs from the Excel design sheet, and preparing the task files.

Frequently Asked Questions about dev-start

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

FAQPage Schema
How do I generate specification documents from an Excel design workbook for feature development?

To generate specification documents from an Excel design workbook, this Skill parses the Excel file using dotnet-script and outputs business and system spec files under docs/specs. It confirms the feature name and item number before creating the files for your repository.

How do I create a feature branch and start a new feature kickoff using Git and GitHub CLI?

To create a feature branch and start a kickoff, this Skill uses Git and GitHub CLI access to automate branch creation. It integrates the branch creation directly with the specification workflow to ensure traceable feature development from the start.

What is the best way to prepare traceable specs and task files for downstream development?

The best way to prepare traceable specs and task files is to generate business and system documents from an Excel design sheet, commit the results, and push them for task construction handoff. This ensures consistent repository structure and ready-to-implement tasks.

Do I need dotnet-script and GitHub CLI to automate branch creation and spec generation?

Yes, you need dotnet-script for Excel parsing and GitHub CLI for branch creation and pushing commits. These tools are required to execute the automated feature kickoff workflow and generate the specification documents.

Can I use this feature kickoff workflow for repository-based projects that do not use an Excel design sheet?

No, this workflow specifically applies to repository-based projects that begin from an Excel design workbook. It requires the Excel file to generate the necessary business and system documents and traceability for the feature.