from-the-other-side-wiggins

Generates audience-aware narrative framing and decision explanations for technical communication.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill from-the-other-side-wiggins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: from-the-other-side-wiggins
Source: https://github.com/github/awesome-copilot/tree/main/skills/from-the-other-side-wiggins
Command: npx skills add https://github.com/github/awesome-copilot --skill from-the-other-side-wiggins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical teams often struggle to explain why decisions were made, producing unclear PR descriptions, design notes, and stakeholder communications that hide weak reasoning behind polished language.

Core Features & Use Cases

  • Decision Narratives: Frames the reasoning behind technical decisions, separating what is known, inferred, and uncertain.
  • Audience Adaptation: Translates technical details for non-technical readers, adjusting abstraction levels for engineers, leaders, and partners.
  • Writing Refinement: Drafts and polishes PR descriptions, design notes, and problem statements with explicit tradeoffs.
  • Use Case: After shipping a complex refactor, ask for a PR description that explains the decision rationale to both the engineering team and product stakeholders.

Quick Start

Ask the assistant to explain why a recent technical decision was made and rewrite the explanation for a non-technical audience.

Frequently Asked Questions about from-the-other-side-wiggins

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

FAQPage Schema
How do I write a PR description that explains technical decisions clearly?

State the decision, name the tradeoffs, and separate what is known from what is inferred or uncertain. This skill drafts structured prose that makes reasoning legible to both engineers and non-technical reviewers.

How to explain technical details to non-technical stakeholders?

Adjust the abstraction level to the audience: engineers need mechanism, leaders need implications and risk, partners need shared language and next steps. The skill reframes the same content for each audience without distorting the underlying reasoning.

When should I use a narrative profile instead of an implementation-focused one?

Use the narrative profile when the work needs meaning and framing rather than execution. Implementation tasks belong to execution-focused profiles, while evidence verification belongs to investigative profiles; this profile finalizes clarity for the target audience.

What are the limitations of narrative framing for technical writing?

Framing can clarify reality or distort it, so it must never make weak reasoning look stronger. The skill explicitly avoids replacing implementation work or evidence analysis and refuses to optimize style at the expense of truth.

Can this profile work together with other assistant personas?

Yes, it coordinates with execution-focused and evidence-focused profiles in a handoff pattern: execution produces early output, evidence review pressure-tests reasoning, and this profile finalizes narrative clarity for the audience.