Skip to content
Skills Library
Programming · Writing

comms-issue

/comms-issue

Use when drafting or updating a Flowstate GitHub issue or design proposal, so it lands as a durable problem statement with evidence and acceptance criteria rather than a transcript.

Repository
flowstate ↗
Licence
MIT
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when drafting or updating a Flowstate GitHub issue or design proposal, so it lands as a durable problem statement with evidence and acceptance criteria rather than a transcript.

Original author description

Use when drafting or updating a Flowstate GitHub issue or design proposal, so it lands as a durable problem statement with evidence and acceptance criteria rather than a transcript.

How it works

  1. Before writing
  2. Default shape
  3. Repository specifics
Original SKILL.md headings · 39 lines, 242 words
SKILL.md preview
---
name: comms-issue
description: Use when drafting or updating a Flowstate GitHub issue or design proposal, so it lands as a durable problem statement with evidence and acceptance criteria rather than a transcript.
---

# Issue communication

An issue is a durable problem statement and decision surface, not a polished
transcript of the investigation.

## Before writing

Read the current issue when one exists. Verify claims against the current tree,
linked incidents, and documentation. Search for duplicate issues and for the
repository's existing spelling of the concept; `docs/DSL.md` records most
language decisions and why they were taken.

## Default shape

1. **Problem or observed behavior** — what is true now and why it matters.
2. **Evidence** — reproducer, diagnostic, code path, measurement, or concrete
   example.
3. **Desired outcome** — observable behavior after the work, not a premature
   implementation prescription.
4. **Acceptance criteria** — conditions a reviewer or test can evaluate.
5. **Constraints and dependencies** — compatibility, threat boundary, rollout,
   or sequencing facts that materially constrain the solution.
6. **Open questions** — only decisions that are genuinely unresolved.

For a design issue, show the smallest concrete sketch that exposes the API or
language shape, then compare alternatives against the existing invariants. Cite
the current source or documentation that makes a constraint real.

## Repository specifics

- Do not hard-wrap GitHub prose; keep each paragraph and list item on one source
  line and let the browser wrap it.
- Keep observation, hypothesis, proposal, and decision separate; a likely
  explanation is not a recorded fact.
- Labels: `kind/bug` needs a reproducer, `kind/design-record` records a decision
  before code, `kind/decision` is the maintainer's call, `kind/umbrella` groups
  slices; area labels say where.

Versions

The database has no other skills named comms-issue.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 2fc6dbb03490 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100comms-pr
    Use when drafting or updating a Flowstate pull request title and body; the body follows the template's six sections and the commit-conventions check reads it.
  • 90comms-commit
    Use when writing or reviewing a Flowstate commit message or squash subject; the shape is a scope prefix, a colon, and a lowercase imperative, with a body that says why, and tools/commitcheck holds it to that shape.
  • 100comms-how
    Explain how a subsystem works, its architecture, runtime flow, and where new code belongs. Use for "how does X work", walkthroughs before changing something, and placement or ownership questions like "where should this live" or "which package owns this". Use comms-why for motivation.
  • 100sl-ds-ticket-to-plan
    Turns a GitHub issue of the SL Design System (sl-design-system/components) into draft acceptance criteria for the developer to confirm, then into an implementation plan mapped to this repository's files. Use it when a design-system developer starts work on an issue, asks what an…
  • 10001-issue
    Strictly draft issues using the mandatory issue template with clear problem context, acceptance criteria, edge cases, and verification plans, saving the raw Markdown to .issue-draft.md. Activate whenever asked to write, draft, or generate an issue (feat:, fix:, refactor:, perf:,…
  • 88fix-github-issue
    Fix a GitHub issue by number. Use when asked to fix GitHub issues.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.