skills.rest
curdx
curdxCOMMUNITY
Explore all skills by this author →
GitHub

communication-style

Standardize concise, scan-friendly writing for curdx-flow artifacts.

4|Updated Apr 26, 2026
Search Tags:#concise writing#phase documentation#spec artifacts#terminal readability#action steps#unresolved questions
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill communication-style-curdx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: communication-style
Source: https://github.com/curdx/curdx-flow/tree/main/plugins/curdx-flow/skills/communication-style
Command: npx skills add https://github.com/curdx/curdx-flow --skill communication-style-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents long, hard-to-scan outputs and inconsistent formatting when producing curdx-flow phase artifacts, so reviews and terminal reads stay efficient.

Core Features & Use Cases

  • Brevity-first writing: favors fragments, bullets, and tables over prose to reduce token count and accelerate scanning.
  • Predictable structure: enforces a consistent order (overview → main content → unresolved questions → last action steps) for bottom-up reading.
  • Sharper collaboration signals: surfaces ambiguities as unresolved questions before prescribing steps, reducing rework during research/requirements/design/tasks/reviews/walkthroughs/progress summaries.

Quick Start

Use the communication-style skill whenever you draft research.md, requirements.md, design.md, tasks.md, reviews, walkthroughs, progress summaries, or subagent phase output.

Frequently Asked Questions about communication-style

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

FAQPage Schema
How do I write concise phase documentation for terminal readability?▼

Writing concise phase documentation for terminal readability requires brevity-first formatting that favors fragments, bullets, and tables over prose to reduce token count and accelerate scanning speed.

What is the standard section order for spec artifacts to ensure bottom-up reading?▼

The standard section order for spec artifacts follows a predictable structure: overview first, then main content, followed by unresolved questions, with action steps placed last for highest visibility and bottom-up reading.

How do I format unresolved questions in requirements or research documents?▼

Format unresolved questions in requirements or research documents by placing them in a dedicated section before action steps, which surfaces ambiguities early and reduces rework during reviews and walkthroughs.

Does concise writing work for progress summaries and walkthroughs in a terminal-first delivery workflow?▼

Concise writing works for progress summaries and walkthroughs in terminal-first delivery by enforcing scan-friendly output with short, structured formatting that keeps reviews efficient across all curdx-flow phase artifacts.

Why put action steps last in task or design documentation?▼

Placing action steps last in task or design documentation ensures highest visibility for bottom-up readers, allowing reviewers to see unresolved questions and context before committing to specific execution steps.

Related Skills

Explore More Content & Communication Skills→
curdxcurdx
4

spec-workflow

Route prompts through research, requirements, design, tasks, and implement phases.

Community
Advanced
u9401066u9401066
2

task-workflow

Automate single-task workflows through PLAN, EXECUTE, VERIFY, and COMPLETE phases.

Community
Intermediate
curdxcurdx
4

curdx-core

Coordinate curdx-flow execution by governing flags, state lifecycle, and subagent delegation.

Community
Advanced
prismaprisma
47.5k

adr-review

Analyze and refine Markdown Architecture Decision Records for clarity and maintainability.

Official
Intermediate