initiative-architecture

Plans massive multi-epic work requests through research spikes, decision logs, and milestone structures.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill initiative-architecture-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: initiative-architecture
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/initiative-architecture
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill initiative-architecture-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Massive work requests that span multiple epics are hard to plan because they contain many unknowns, undocumented decisions, and no resumable structure. This Skill turns such requests into a tractable, documented architecture that a fresh context can pick up and continue. ## Core Features & Use Cases - Unknown Documentation: Categorizes every unknown as Critical, Important, or Nice-to-Know and creates a GitHub initiative tracking issue. - Research Spikes: Creates time-boxed spike issues for each unknown, captures findings, and records recommendations. - Decision Log & Epic Structure: Records every decision with options, rationale, and reversibility, then groups deliverables into epics with dependencies and milestones. - Use Case: A request like "add phone popup login" becomes an initiative with spikes investigating mobile app status, push infrastructure, and auth security, followed by epics for the app, push system, and auth flow assigned to delivery milestones. ## Quick Start Ask the assistant to use initiative-architecture to plan your massive multi-epic request, starting by documenting all unknowns in a GitHub tracking issue.

Frequently Asked Questions about initiative-architecture

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

FAQPage Schema
How do I plan a massive software project with many unknowns?▼

Start by documenting every unknown in a tracking issue, categorized as Critical, Important, or Nice-to-Know. Then create time-boxed research spike issues for critical unknowns, record decisions in a decision log, and group deliverables into epics with milestones.

What is a research spike in project planning?▼

A research spike is a time-boxed investigation created to answer a specific unknown blocking architecture or implementation. Each spike documents findings, provides a recommendation, and identifies the decision it enables before being closed.

When should work be an initiative instead of an epic?▼

Work becomes an initiative when it spans multiple epics, requires significant research before planning, may need new infrastructure, and will take weeks to months. Single-epic work should use standard epic management instead.

How does the initiative stay resumable across sessions?▼

The initiative tracking issue contains a context recovery section listing open spikes, the decision log, current phase, and the next action. A fresh context reads this issue plus linked spikes to continue without prior conversation history.

Does this planning approach require GitHub?▼

Yes, the workflow uses the GitHub CLI to create initiative tracking issues, spike issues, labels, and milestones. Decision logs and findings are stored as issue bodies and comments within the repository.