Przejdź do treści
Biblioteka skilli
Dokumenty i biuro · Pisanie

co-write-document

/co-write-document

Pomaga napisać obszerny dokument z użytkownikiem: zbiera kontekst, uzgadnia plan i sprawdza tekst na świeżym czytelniku.

Repozytorium
yaap ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga napisać obszerny dokument z użytkownikiem: zbiera kontekst, uzgadnia plan i sprawdza tekst na świeżym czytelniku.

Oryginalny opis (EN)

Write a substantial document with the user (a proposal, design, report, guide, policy or long email) by gathering context, agreeing on an outline, drafting section by section and testing it on a fresh reader. Use it whenever the user asks to draft or rework a document others will read and act on.

Jak działa

  1. 1. Gather the context
  2. 2. Agree on an outline
  3. 3. Write section by section
  4. 4. Test on a fresh reader
  5. 5. Final pass
  6. Report
Sekcje z nagłówków SKILL.md, w oryginale · 80 linii, 683 słów
Podgląd SKILL.md
---
name: co-write-document
description: Write a substantial document with the user (a proposal, design, report, guide, policy or long email) by
  gathering context, agreeing on an outline, drafting section by section and testing it on a fresh reader. Use it
  whenever the user asks to draft or rework a document others will read and act on.
license: MIT
metadata:
  sources: own
---

# Co-write a document

A good document comes from knowing its reader and its purpose, then building it in parts the user can steer. Writing
it all at once and asking "is this good?" leaves the user to find every gap alone.

## 1. Gather the context

Before writing anything, find out:

- **Purpose.** What should the reader know, decide or do after reading it?
- **Reader.** Who reads it, what do they already know, and how much time will they give it?
- **Shape.** Is there a template, a length, a format, a deadline? Is it a new document or a rework of one?
- **Material.** What exists already: notes, earlier versions, attachments, files in the project, knowledge sources,
  conversations. Ask the user to share it, unsorted is fine.

Ask the few questions that matter, a couple at a time, not a long form. Read the material the user gives you
(`read_attachment`, `read_file`, `read_knowledge`) before asking what it already answers. Note open questions and
move on when you have enough to outline; the rest can be asked per section.

## 2. Agree on an outline

Propose the headings, each with one line on what it holds and why the reader needs it. Put the point of the whole
document in the first section. Keep the outline short enough to change easily; changing an outline costs little,
rewriting finished sections does not.

Write it to a Markdown file in the project. When `open_document` is available (in a project conversation), open the
file with it, so the user can read and edit it beside the chat; their saved edits reach you, so build on them rather
than on your own earlier text. Otherwise keep the draft in the reply and show each changed section again after a
round of edits.

## 3. Write section by section

Start with the section that carries the most uncertainty or the core argument, not necessarily the first. For each
section:

1. Ask what must go in, if the material does not settle it. Offer a short list of candidate points and let the user
   keep, drop or add.
2. Draft the section in the document (or in the reply).
3. Ask for changes. Apply them precisely; when the user rewrites a passage, keep their wording and learn their style
   from it for the next sections.
4. Move on when the user is satisfied. Do not polish one section while the others are empty.

When the user's edits show a preference (shorter, more formal, no bullet lists), apply it to the whole document and
say so.

## 4. Test on a fresh reader

You and the user know too much to read it as a newcomer. When `delegate` is available (in a project conversation),
use an exploring worker: it does not see this conversation, so it reads the document as the intended reader would.
Otherwise suggest that the user gives it to a colleague who has not seen it. Give the reader the file, a one-line
description of who they stand in for, and ask:

- What is this document asking of you, in one sentence?
- Which part was unclear, and where did you have to guess?
- What question would you still ask the author?

Compare its answers with the purpose from step 1. Where they differ, the document is unclear, not the reader. Fix
those places and, for a large change, test once more.

## 5. Final pass

- The point is in the first lines; each section starts with its own point.
- Cut what this reader does not need; link to detail instead of including it.
- Terms, names and numbers are consistent throughout; every fact that needs one has its source.
- Every request has an owner and, where it matters, a date.

Follow the `writing` standard when the Blueprint has it (`load_standard`).

## Report

End with this shape:

```
Document: <path>
Reader test: <what the fresh reader got right, and what was unclear>
Changed after the test: <the fixes, or "nothing">
Open: <questions the user still has to answer, or "nothing">
```

Wersje

W bazie nie ma innych skilli o nazwie co-write-document.

Migawka bazy z 13.11.2026 · wersja paczki d7c1c37f3946 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100write-docs
    Prowadzi współpracę nad dokumentem: zbiera kontekst, układa strukturę i sprawdza, czy czytelnik bez znajomości sesji rozumie tekst.
  • 100doc-coauthoring
    Pomaga wspólnie pisać specyfikacje techniczne, RFC, PRD, ADR i dokumenty decyzyjne: zbiera kontekst, iteracyjnie dopracowuje treść i testuje ją na ślepym czytelniku.
  • 100write-docs
    Pisze lub poprawia dokumentację deweloperską: README, przewodnik, instrukcję lub wyjaśnienie, sprawdzając ją na nowicjuszu.
  • 90doc-coauthoring
    Współtworzy dokumenty ustrukturyzowane, jak propozycje, specyfikacje i decyzje, w trzech etapach: kontekst, plan, szkice sekcji i symulacja czytelnika.
  • 90document-delivery
    Przygotowuje dokumenty do konkretnego odbiorcy: najpierw plan, a każde twierdzenie ma źródło lub oznaczenie założenia.
  • 100doc-coauthoring
    Pomaga współtworzyć dokumenty, takie jak propozycje i specyfikacje techniczne, oraz dopracowywać dokumentację w prowadzonej współpracy.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.