amplify-planning

Name: amplify-planning
Availability: InStock
Author: nexar

Enforce a two-document strategy and implementation planning workflow with approval gates.

Updated Aug 23, 2026

Search Tags:#workflow #planning #templates #documentation #strategy #approval

Ready to run

npx skills add https://github.com/getnexar/decrypt-tool --skill amplify-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amplify-planning
Source: https://github.com/getnexar/decrypt-tool/tree/main/ai-tools/skills/amplify-planning
Command: npx skills add https://github.com/getnexar/decrypt-tool --skill amplify-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Amplify Planning solves the problem of unaligned project scope by enforcing a two-document workflow (strategy and implementation plan), ensuring the rationale for decisions is captured and approved before details are executed.

Core Features & Use Cases

Strategy-before-tactics: document why before what to reduce misalignment.
Two-document workflow: create a strategy document first and require approval before the implementation plan.
Governance and risk management: capture alternatives, decisions, and approval criteria to guide development.

Quick Start

Create the strategy document first using the provided template, then draft the implementation plan only after strategy approval.

Frequently Asked Questions about amplify-planning

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

FAQPage Schema

How do I enforce a strategy-first planning process for feature approvals?▼

Strategy-first planning is enforced by capturing the rationale for decisions in a strategy document that requires approval before any implementation plan is drafted, reducing misaligned project scope.

What is the best way to document feature rationale before implementation begins?▼

Documenting feature rationale works best by creating a strategy document first to capture alternatives, decisions, and approval criteria, effectively guiding development and reducing misalignment before execution.

How do I set up a two-document workflow for product initiatives?▼

Set up a two-document workflow by creating a strategy document first using a provided template, then drafting the implementation plan only after the strategy document successfully passes the required approval gates.

Does this strategy planning workflow require approval gates for architectural changes?▼

Yes, the strategy planning workflow enforces approval gates specifically for non-trivial product initiatives and architectural changes, ensuring strategy must precede implementation and be formally approved before work begins.

Can I apply approval gates and templates to manage unaligned project scope?▼

Yes, you can apply approval gates and templates to manage unaligned project scope by enforcing a strategy-first workflow that captures decisions and rationale before implementation details are executed.

When should I not use a two-document strategy and implementation workflow?▼

A two-document strategy and implementation workflow should not be used for trivial features that lack architectural changes, as the overhead of strategy documentation and formal approval gates outweighs the governance benefits for simple tasks.