stacksmith-plan

Plan end-to-end feature development with OpenSpec-based change tracking.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/TimLai666/skills --skill stacksmith-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacksmith-plan
Source: https://github.com/TimLai666/skills/tree/main/stacksmith-plan
Command: npx skills add https://github.com/TimLai666/skills --skill stacksmith-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating feature development across ideation, scope, architecture, and convergence artifacts to reduce misalignment and rework.

Core Features & Use Cases

  • End-to-end planning across modes: ideate, ceo, eng, design, and auto to ensure explicit scope and milestones.
  • Convergence artifact creation: guides delivery-plan.md, AGENTS.md, CLAUDE.md, and OpenSpec proposals for traceable progress.
  • Handoff and synchronization: maintains a living update loop with blockers, status, and next verifiable outputs for multi-agent collaboration.

Quick Start

Provide a feature concept and run /stacksmith-plan eng to begin architecture planning and artifact convergence.

Frequently Asked Questions about stacksmith-plan

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

FAQPage Schema
What is feature convergence planning and when do I need it?

Feature convergence planning coordinates ideation, scope, architecture, and milestones to reduce misalignment and rework. You need it when managing end-to-end feature development across multiple modes and requiring explicit risk assessment with traceable artifacts.

How do I start architecture planning using OpenSpec proposals?

To start architecture planning, provide a feature concept and run the engineering mode to begin artifact convergence. This guides creation of delivery-plan.md, AGENTS.md, CLAUDE.md, and OpenSpec proposals for traceable progress.

Can I use this for multi-agent collaboration and handoff synchronization?

Yes, you can use it for multi-agent collaboration through a living update loop that maintains blockers, status, and next verifiable outputs. The handoff loop ensures synchronization and artifact provenance across coordinated agents.

Does OpenSpec-based change-by-change planning work without external dependencies?

OpenSpec-based change-by-change planning operates independently without external dependencies. It enforces explicit scope and milestone-driven outputs across ideate, ceo, eng, design, and auto modes to ensure structured feature convergence.

What's the best way to coordinate feature development across ideation and delivery?

The best way to coordinate feature development is using structured modes that ensure explicit scope, risk assessment, and milestone-driven outputs. This approach maintains artifact provenance through a delivery plan and handoff loop for verifiable progress.

Why does feature development require explicit scope and risk assessment?

Feature development requires explicit scope and risk assessment to reduce misalignment and rework during convergence. Without milestone-driven outputs and artifact provenance, coordinated planning across ideation and architecture becomes fragmented and unverifiable.