strategic-planner

Generate strategic specifications and implementation plans for data architecture projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zazu-22/ff_data_analytics --skill strategic-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategic-planner
Source: https://github.com/zazu-22/ff_data_analytics/tree/main/.claude/_archive_skills/strategic-planner
Command: npx skills add https://github.com/zazu-22/ff_data_analytics --skill strategic-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill designs comprehensive technical specifications and strategic plans for data architecture and analytics projects, following SPEC formats. It guides requirements gathering, MoSCoW prioritization, phased architecture, and open-items tracking.

Core Features & Use Cases

  • SPEC/document creation workflow with background, requirements (MoSCoW), method, success metrics
  • Architecture planning, phase definitions, and open-items tracking
  • ADR references linking to architectural decisions and related specs

Quick Start

Use Strategic Planner to draft SPEC documents (e.g., SPEC-1) and attach open-items/tracking sections. Start with assets/spec_template.md to populate basic structure.

Frequently Asked Questions about strategic-planner

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

FAQPage Schema
How do I create a SPEC document with MoSCoW prioritization for a data architecture project?

SPEC documents organize requirements using MoSCoW prioritization (Must, Should, Could, Won't) alongside background, phased implementation method, and success criteria. Strategic Planner generates this structure automatically, linking architectural decisions and tracking open items across phases.

What should I include in a strategic specification for a greenfield analytics project?

A strategic specification includes background context, functional requirements organized by MoSCoW priority, detailed architecture and phased implementation method, measurable success criteria, references to architectural decision records (ADRs), and an open-items tracking section for iterative refinement.

Can I use Strategic Planner to track open items and dependencies across implementation phases?

Yes. Strategic Planner structures open-items tracking within SPEC documents, enabling you to document unresolved requirements, dependencies, and decisions across each phase of your plan, with links to related ADRs and prior specifications.

How do I organize phased implementation for a data migration or major feature spec?

Strategic Planner breaks implementation into distinct phases within the Method section, assigning requirements to phases based on MoSCoW priority and dependency order. Each phase includes concrete architecture details and success metrics tied to your overall plan.

What's the difference between using MoSCoW prioritization versus sequential requirement listing?

MoSCoW prioritization separates critical, required work (Must) from valuable enhancements (Should/Could) and out-of-scope items (Won't), reducing scope creep and clarifying trade-offs. SPEC format enforces this discipline, making phased delivery and resource planning explicit and traceable.