Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Analiza

shape-idea

/shape-idea

Odtwarza pomysł na trzecim kroku ścieżki odkrywania, pokazuje opcje, kompromisy i zalecenie.

Repozytorium
paqad-ai ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

90/ 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ść25 / 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
8
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.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

Odtwarza pomysł na trzecim kroku ścieżki odkrywania, pokazuje opcje, kompromisy i zalecenie.

Oryginalny opis (EN)

Chat and Claude Code: Step 3 of the discover journey: plays the idea back with options, trade-offs and a recommendation. Use when the journey directs it to step 3, not directly.

Jak działa

  1. When this runs
  2. What it does
  3. If the checks cannot run
  4. Output
Sekcje z nagłówków SKILL.md, w oryginale · 75 linii, 775 słów
Podgląd SKILL.md
---
name: shape-idea
description: "Chat and Claude Code: Step 3 of the discover journey: plays the idea back with options, trade-offs and a recommendation. Use when the journey directs it to step 3, not directly."
compatibility: "claude.ai chat, Cowork or Claude Code; reads project docs and code through a connector, uploaded files or the open folder"
---

# shape-idea

How to talk: follow `references/voice.md`. Short, answer first, plain business words, no narration,
one short sources line. Those rules win.

## When this runs

Directed by the discover journey, not started directly: step 3, after the idea and today blocks are
in the record. Say the status on entry ("Step 3 of 6: shaping the idea.").

## What it does

Shape the idea, do not just repeat it, working only from the idea and today blocks and what the user
said. Raise conflicts kindly (`references/challenge-guide.md`).

1. When the today block carries `comparison` marks, open the playback with them, before any
   question: the agree, tickets only, repository only and differ lines, one line each, with the
   wording from step 2. With no marks show no comparison lines and no empty heading; in a
   tickets-only run label each fact as from the tickets. Then play the idea back, goal first. Use the shape in `references/playback-template.md`: the goal,
   what exists today (including what the docs could not confirm), the options with their
   trade-offs in business terms, a smaller first step where it helps, and a recommendation. Call
   an area the documents do not cover not documented; never say or imply it is not built. Code
   lines keep "the code suggests" ("What the documents prove" in `references/paqad-docs-map.md`).
   Ticket lines keep "the tickets say" and their issue keys (`references/ground-from-tracker.md`). Evidence stays at its level, with
   the run's one source line (`references/evidence-levels.md`). End with the sources line, then the
   closing question through the choice prompt.
2. Look through the expert lenses (`references/expert-lenses.md`): customer value and experience,
   business and cost, operations and support, data and privacy, security and access, and rollout
   and change for existing users. Raise only what matters, in business terms, each with a
   recommendation. Name a privacy or security risk (such as customer personal data leaving the
   product) plainly with what you would do about it.
3. Offer options through the host's choice prompt, each with a few-word trade-off (time, cost, risk,
   effect on users), the recommended one marked with a short why.
4. When the idea is large or uncertain, offer a smaller first release or an experiment with a
   success condition that would justify going further.
5. If the idea already exists as a documented capability, or a code-suggests line in the today block
   shows it exists, say so with the source (keeping "the code suggests" on code lines), recommend the
   already-exists outcome and draft nothing more unless asked. A ticket line alone never gives
   that outcome, even for a ticket marked done: say "the tickets say this was finished" with the
   key, and recommend checking with the team before building again.
6. Raise a disagreement between the code or docs and the tickets once, as a challenge with a
   recommendation that follows the code and docs, never the tickets; the differ line names the
   issue key and ends "I'm going with the code and docs."
7. Label every suggestion as one; nothing enters the record until accepted. Respect an informed
   choice; revisit it only for new evidence.

## If the checks cannot run

No script; shape by hand with this checklist:

- Playback: goal, today, options and trade-offs, smaller first step where useful, recommendation,
  sources line, closing question last.
- Options and the way forward on a challenge are offered through the choice prompt (a short list
  in the reply only when the host has none), the recommended one marked.
- Each of the six lenses was considered; the ones that matter for this idea are raised in
  business terms with a recommendation, the rest left out.
- A real risk, conflict or duplicate is named with its evidence and a way forward.
- Where the idea is large or uncertain, a smaller first release or experiment with a success
  condition is offered.
- If the idea already exists, that is said with the source and the already-exists outcome is
  recommended. A ticket line alone, even a done ticket, never gives that outcome: recommend
  checking with the team first.
- Ticket lines keep "the tickets say" and their keys. A disagreement between the repository and
  the tickets is raised once, and the repository wins.
- "What the documents prove" (`references/paqad-docs-map.md`) by hand: call an area the today block
  does not document not documented; never say or imply it is not built. Code lines keep "the code
  suggests".
- Every suggested measure or scope cut is labelled a suggestion and only recorded once accepted.

## Output

The content of the playback block: goal-first playback, lens notes, options with trade-offs, the
smaller first step and the recommendation. discover writes it once the user accepts the shaping.
Pliki w paczce (8)
  • SKILL.md 5 KB
  • references/challenge-guide.md 2 KB
  • references/evidence-levels.md 5 KB
  • references/expert-lenses.md 2 KB
  • references/ground-from-tracker.md 6 KB
  • references/paqad-docs-map.md 7 KB
  • references/playback-template.md 3 KB
  • references/voice.md 4 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · eliyce/paqad-ai90MIT
tojim00d/Orbit-skills100MIT
eliyce/paqad-ai90MIT

Migawka bazy z 13.11.2026 · wersja paczki 445c4282ac62 (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

  • 90ground-in-project
    Zapisuje stan istniejący dla pomysłu z dokumentów i kodu projektu, z podaniem źródeł, w drugim kroku ścieżki odkrywania.
  • 90understand-idea
    Doprecyzowuje cel, odbiorców, sukces i ograniczenia pomysłu na produkt jako pierwszy krok procesu odkrywania.
  • 100journey-idea
    Prowadzi pierwszy etap ścieżki Butterbase dla surowego pomysłu: burzę mózgów pytanie po pytaniu o użytkownika i must-have'y, z tagami funkcji Butterbase, i tworzy docs/butterbase/01-idea.md.
  • 100idea-genie
    Wymyśla opcje poparte dowodami na to, co budować, albo poddaje pomysł testowi wytrzymałości, także przy porównywaniu opcji.
  • 100shape
    Zamienia surowy pomysł w plan przed budową: wywiad w rundach, zakres, stos i krótki dokument projektu do zatwierdzenia.
  • 100forge-shape
    Przekształca niejasny pomysł w konkretny plan przez badanie bazy kodu i pytania zadawane po jednym, zanim powstanie zgłoszenie.

Uwagi i zgłoszenia

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