charter

Writes PRDs, user stories, and prioritized backlogs from vague product ideas.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/kridaydave/My_Skills --skill charter-kridaydave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: charter
Source: https://github.com/kridaydave/My_Skills/tree/main/charter
Command: npx skills add https://github.com/kridaydave/My_Skills --skill charter-kridaydave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often build features before validating the underlying problem, wasting engineering effort on solutions nobody needs. Charter turns vague ideas into problem-first product specs with measurable success criteria, explicit scope cuts, and testable acceptance criteria before design or coding begins. ## Core Features & Use Cases - PRD and Spec Writing: Produces problem-first PRDs with success metrics, MoSCoW scope tables, MVP definitions, acceptance criteria, and kill conditions. - Backlog Prioritization: Ranks feature requests using RICE, value-vs-effort, or MoSCoW frameworks with explicit cut lines and flagged low-confidence assumptions. - Requirement Challenging: Reverse-engineers solution-shaped requests back to the real user problem and pushes back on scope creep, missing metrics, and sunk-cost momentum. - Use Case: A stakeholder asks for a notifications center. Charter identifies the actual problem (users missing critical updates), proposes cheaper alternatives, and scopes a minimal test before committing sprints of build work. ## Quick Start Ask Charter to turn your feature idea into a PRD with a problem statement, success metric, prioritized scope, and acceptance criteria.

Frequently Asked Questions about charter

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

FAQPage Schema
How do I write a PRD from a vague feature idea?▼

Start with the problem, not the solution: name the specific user, their pain, and the evidence it is real. Then define a measurable success metric, scope with MoSCoW priorities, write testable Given/When/Then acceptance criteria, and state a kill condition.

How do I prioritize a product backlog with RICE?▼

Score each item on Reach, Impact, Confidence, and Effort, then rank by the computed score. Present the ranked table with a clear recommendation of what to do, defer, and drop, and flag the lowest-confidence input the ranking depends on.

What is the difference between an MVP and a first version?▼

An MVP is the cheapest experiment that tests the riskiest assumption, not a polished version one. If the bet is that users will pay, the MVP proves willingness to pay rather than delivering a complete feature set.

When should a feature request be rejected or cut?▼

Cut a feature when there is no identifiable user, no measurable outcome, or when it serves a tiny edge case while complicating the core flow. Also reconsider when beta usage is near zero and sunk cost is the only argument for continuing.

Does Charter design or implement the solution?▼

No. Charter decides what to build and why, producing the problem statement, scope, and acceptance criteria. Solution design is explicitly handed off to a design persona and implementation to an engineering persona.