new-eng-feature

Orchestrate a five-step feature planning workflow with sequential skills.

1|Updated Jun 7, 2024
One-click install
npx skills add https://github.com/jsco2t/dotfiles --skill new-eng-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-eng-feature
Source: https://github.com/jsco2t/dotfiles/tree/main/.claude/skills/new-eng-feature
Command: npx skills add https://github.com/jsco2t/dotfiles --skill new-eng-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end feature planning often requires coordinating multiple specialized skills and artifact management. This skill creates a single, structured documentation folder and orchestrates five sequential skills (/eng-plan-creator, /eng-design-creator, /eng-test-planning, /eng-task-planning, /eng-verification-creator), passing outputs forward and preserving index integrity while routing all interactive Q&A to the user.

Core Features & Use Cases

  • Orchestrates the complete planning pipeline in five steps: plan creation, design, test planning, task planning, and verification.
  • Maintains interconnected artifacts (plans, design, task plan, and verification docs) and updates their corresponding indices.
  • Supports interactive Q&A flow to capture requirements and design decisions, ensuring decisions propagate through each stage.

Quick Start

Provide the required inputs (output directory, spec links, and code repository path) and run the pipeline in the exact order: plan creator, design creator, test planning, task planning, then verification.

Frequently Asked Questions about new-eng-feature

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

FAQPage Schema
How do I orchestrate end-to-end feature planning across multiple engineering teams?

End-to-end feature planning is orchestrated by executing five sequential skills—plan creation, design, test planning, task planning, and verification—within a single documentation folder. This pipeline enforces strict execution order and routes interactive Q&A directly to the user to capture cross-team requirements.

What is the best way to maintain index integrity when generating interconnected engineering planning documents?

To maintain index integrity during feature planning, the workflow preserves predetermined output paths and updates corresponding indices automatically as interconnected artifacts are generated across the plan, design, test, task, and verification stages.

How do I automate the creation of design, test, and task planning artifacts for a new software feature?

Automating artifact creation for a new feature requires running an orchestrated pipeline that sequentially generates planning, design, test, task, and verification documents, passing outputs forward to ensure decisions propagate through each engineering stage.

Do I need to provide a code repository path and spec links to start automated feature planning?

Yes, starting automated feature planning requires providing the output directory, specification links, and the code repository path. These inputs initialize the pipeline and enable the sequential execution of the five planning skills.

Can I use this workflow automation for features requiring complex design decisions and cross-team input?

Yes, this workflow automation is specifically applicable to new features requiring cross-team input, design decisions, and verification across planning, design, testing, and task breakdown. It uses an interactive Q&A flow to capture and propagate those decisions.