magnus-add-growth-story

Create client growth story Markdown files and update the impact index grid.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ssu96ld/magnus-claude-plugins --skill magnus-add-growth-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: magnus-add-growth-story
Source: https://github.com/ssu96ld/magnus-claude-plugins/tree/main/plugins/magnus-site/skills/magnus-add-growth-story
Command: npx skills add https://github.com/ssu96ld/magnus-claude-plugins --skill magnus-add-growth-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating transparent client growth stories is time-consuming and error-prone when teams manually draft Markdown, manage routing, and surface results on the impact index. This Skill automates the end-to-end workflow with standardized frontmatter, a CsCard update, and mandatory approvals.

Core Features & Use Cases

  • Generates a Markdown file at src/content/growth-stories/<client>/<slug>.md that conforms to the canonical zod schema and renders in /impact/growth-story/[...slug].
  • Inserts a matching CsCard at the top of the /impact index grid, surfacing client outcomes.
  • Enforces double sign-off: one for the story, one for the client metric, ensuring client confidentiality and governance.
  • Automatically updates the impact index and navigational paths after creation.

Quick Start

Provide the client name and slug, and I will scaffold the growth story and update the impact index.

Frequently Asked Questions about magnus-add-growth-story

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

FAQPage Schema
How do I create a client growth story with double sign-off in Markdown?▼

To create a client growth story, this workflow scaffolds a Markdown file at src/content/growth-stories/<client>/<slug>.md, updates the impact index grid with a CsCard, and enforces a mandatory double sign-off for client metrics and story publication.

How do I add a new case study card to an Astro impact index page?▼

Adding a case study card is automated by inserting a matching CsCard at the top of the /impact index grid in src/pages/impact/index.astro, ensuring the client outcomes are surfaced immediately upon story creation.

What is the double sign-off process for publishing client metrics?▼

The double sign-off process requires two separate mandatory approvals before publication: one authorizing the client growth story itself and another validating the real client metrics, ensuring strict governance and confidentiality.

Does this growth story workflow validate Markdown frontmatter and slug formats?▼

Yes, this workflow validates slug formats and ensures Markdown frontmatter conforms to the canonical zod schema, guaranteeing that the generated content renders correctly at the /impact/growth-story/[...slug] route.

Can I use this to automate routing for client outcomes without manual configuration?▼

Yes, you can automate routing entirely. The process automatically updates navigational paths and writes files directly into the Astro content structure, eliminating manual routing configuration for new growth stories.