Agent skill
mds-messaging-direction-summary
Produces the Messaging & Direction Summary covering product pitch, features/benefits, use cases, audiences, value props, objections, brand pitch, competitive notes, USP, desired emotions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/mds-messaging-direction-summary
SKILL.md
Messaging & Direction Summary (MDS)
This skill compiles the MDS document used as the source of truth for campaign messaging.
Input Variables
- [PRODUCT_BIBLE]
- [PERSONA_DATA]
- [COMPETITOR_DATA]
The Protocol
- Product Pitch: succinct hero description.
- Features & Benefits: detailed list with why it matters.
- Use Cases: specific scenes and contexts.
- Target Audiences: demographics and interests.
- Value Propositions: functional, emotional, self-expressive reasons.
- Potential Objections: concerns and rebuttals.
- Brand Pitch: mission and ethos.
- Competitive Notes: similarities and differences.
- USP: unique claim and supporting proof.
- Desired Emotional Response: target feelings.
Output Instructions
Render into templates/mds.md. Do not omit sections. Include a handoff JSON block.
Integration & Technical Specs
API Specification
- ID:
mds-messaging-direction-summary - Path:
skills/mds-messaging-direction-summary/templates/mds.md - Context: Part of Product Detailing
Data Flow
- Input: Derived from project context and upstream skills.
- Output: Generates
mds.md.
CLI Usage
bun scripts/cli.ts activate mds-messaging-direction-summary
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?