smith-new

Coordinate feature development from requirements gathering to autonomous build.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-new
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smith-new
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-new
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end feature development from idea to autonomous build. This skill coordinates requirements gathering, planning, a questions gate, and then autonomous handoff to execution, all within a structured workflow to ensure traceability.

Core Features & Use Cases

  • Conversational requirements gathering that narrows vague concepts into concrete features.
  • Built-in questions gate to surface uncertainties and capture decisions before proceeding.
  • Autonomous execution pipeline that moves from requirements to plan to implementation to review, with artifacts stored in a per-feature .specify directory.
  • Per-worktree isolation to keep the main repository pristine while validating complex features.
  • Logging and auditing hooks that record session events and decisions for traceability.

Quick Start

Describe the feature you want to build to start the smith-new workflow.

Frequently Asked Questions about smith-new

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

FAQPage Schema
How do I automate feature workflows from idea to build?▼

To automate feature workflows, describe the feature you want to build to start the conversational requirements gathering, which then guides planning, a questions gate, and autonomous handoff to execution.

How does requirements gathering work for autonomous feature development?▼

Requirements gathering uses a conversational approach to narrow vague concepts into concrete features, followed by a built-in questions gate to surface uncertainties and capture decisions before proceeding to implementation.

Can I isolate feature development to keep my main repository clean?▼

Yes, you can isolate feature development using per-worktree isolation, which keeps the main repository pristine while validating complex features during the autonomous build process.

Where are planning and implementation artifacts stored during feature management?▼

Planning and implementation artifacts are stored in structured .specify directories within a per-feature repository structure, ensuring traceability throughout the development workflow.

What is the best way to ensure traceability during automated build execution?▼

The best way to ensure traceability is using a structured workflow with logging and auditing hooks that record session events and decisions, alongside structured artifacts stored in .specify directories.

Does this workflow support automated handoff to execution?▼

Yes, the workflow supports autonomous handoff to execution, moving sequentially from requirements to plan to implementation to review while maintaining per-worktree isolation.