actionable-communication

Structure SDLC handoffs, blockers, and reports into decision-ordered actionable messages.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill actionable-communication-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: actionable-communication
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/actionable-communication
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill actionable-communication-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Consequential SDLC communication—handoffs, blockers, completion reports, and requirements—often buries the outcome under preamble, making it hard for the next person to act. This Skill restructures such communication into a compact control surface that leads with the outcome, evidence, and next action. ## Core Features & Use Cases - Decision-ordered writing: Leads with the outcome, blocker, or decision needed, followed by lifecycle phase status, evidence, unresolved items, and a single named next action. - Actionable failure reports: Formats errors as cause, evidence, and remedy, separating known causes from hypotheses and never inventing certainty or dates. - Handoff contract: Provides a five-field template (Outcome, Phase, Evidence, Open, Next) for phase transitions between SDLC roles. - UWDS reference standard: Loads a full Unified Writing and Documentation Standard for formal documentation, requirements, procedures, interface content, and accessibility-sensitive material. - Use Case: After finishing a testing phase, an engineer reports: the verdict, the failing test evidence, the one acceptance-blocking issue, and the named owner of the fix—without conversational filler. ## Quick Start Use the actionable-communication skill to turn this testing phase report into a clear handoff with outcome, evidence, and next action.

Frequently Asked Questions about actionable-communication

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

FAQPage Schema
How do I write an actionable status report for a project handoff?▼

Lead with the outcome or blocker, state the lifecycle phase and its completion status, provide evidence such as artifacts or command results, list only acceptance-affecting open items, and name one next action with its owner.

How should I report a technical error so others can act on it?▼

Report the narrowest supported cause, the evidence such as the failing command or observation, and the smallest remedy likely to unblock progress. Separate known causes from hypotheses and mark missing evidence as unknown.

When should I load the full UWDS writing standard instead of the compact rules?▼

Load the UWDS reference for formal documentation, requirements, procedures, interface content, safety or accessibility content, or scoped standards questions. Simple statuses, blockers, and handoffs use only the compact rules.

Does this skill apply to routine casual conversation?▼

No. Routine conversation follows the host's lightweight communication defaults. The skill activates only for consequential communication such as handoffs, blockers, completion reports, requirements, and formal documentation.

What style guides does the UWDS standard draw on?▼

UWDS synthesizes sources including Google and Microsoft documentation style guides, WCAG 2.2, ISO plain-language standards, RFC 2119 requirement keywords, and AP style for news, with a defined precedence order for conflicts.