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

design

/design

Zamienia pomysły i wymagania w pisemny projekt techniczny, PRD, plan wdrożenia i listę zadań w docs/feat/wip przed kodowaniem.

Repozytorium
claude-toolbox ↗
Licencja
Apache-2.0
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
37
Skrypty
0
Komentarze HTML
1
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

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Zamienia pomysły i wymagania w pisemny projekt techniczny, PRD, plan wdrożenia i listę zadań w docs/feat/wip przed kodowaniem.

Oryginalny opis (EN)

TRIGGER when: asked to write or refine a technical design, PRD, specification, implementation plan, or task list, or resume an existing docs/feat/wip feature. Turns ideas and requirements into written design documents, implementation plans, and tasks in docs/feat/wip/ before coding. For conversational exploration without written planning, use $kk:brainstorm.

Jak działa

  1. Conventions
  2. Workflow
  3. Ideas and Prototypes
  4. Continue WIP Feature
Sekcje z nagłówków SKILL.md, w oryginale · 51 linii, 613 słów
Podgląd SKILL.md
---
name: design
description: |
  TRIGGER when: asked to write or refine a technical design, PRD, specification, implementation plan, or task list, or resume an existing docs/feat/wip feature.
  Turns ideas and requirements into written design documents, implementation plans, and tasks in docs/feat/wip/ before coding. For conversational exploration without written planning, use $kk:brainstorm.
---
<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh -->

# Task Analysis Process

**Goal: Before writing any code, make sure you understand the requirements and have an implementation plan ready.**

## Conventions

- **Read capy knowledge base conventions** at [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md).
- **Read verification policy** at [shared-verification-policy.md](shared-verification-policy.md) before choosing checks or acceptance criteria.
- **Read profile detection** at [shared-profile-detection.md](shared-profile-detection.md). When an active profile contributes a `design/` subdirectory (e.g., `../../profiles/k8s/design/`), its `questions.md` feeds the idea-refinement question pool and its `sections.md` lists required sections the design document must cover. Both the idea-to-design and continue-WIP flows consult the shared procedure; see each flow's workflow file for the specific integration points.

For fresh ideas, two reference files provide methodology and evaluation rubric: [shared-ideation-frameworks.md](shared-ideation-frameworks.md) (ideation lenses for the diverge phase) and [shared-idea-refinement-criteria.md](shared-idea-refinement-criteria.md) (evaluation dimensions and MVP scoping for the converge phase). These are loaded during the instruction-load step and consumed by idea-process.md Step 3 sub-phases.

## Workflow

**Mandatory order — understanding before engagement.** The flow below is strictly sequential. Do not engage with idea prose beyond a keyword scan, read WIP document content, ask refinement questions, or write design content until all instructions — this SKILL.md, the relevant process file, the shared protocols, every resolved profile's `design/` content, and the fresh-idea references below (when applicable) — are fully loaded. Bounded signal inspection for profile detection is the only content-read exception.

The `$kk:design` skill has two entry points; each has its own process file with a detailed workflow. Both follow the same mandatory ordering:

1. **Keyword scan only.** The idea prose (or WIP feature directory) is scanned at the keyword/filename level — enough to drive profile detection, not enough to engage with the content.
2. **Load instructions.** Read the relevant process file ([idea-process.md](./idea-process.md) or [existing-task-process.md](./existing-task-process.md)), the shared protocols above and [example-tasks.md](./example-tasks.md) (task format), even on an unchanged resume.
  - For WIP, also load the drafting guidelines in idea-process.md for potential refinement, without running its fresh-idea sub-phases.
  - For fresh ideas, also read [shared-ideation-frameworks.md](shared-ideation-frameworks.md) (ideation lenses) and [shared-idea-refinement-criteria.md](shared-idea-refinement-criteria.md) (evaluation rubric).
3. **Detect active profiles.** Delegate to [shared-profile-detection.md](shared-profile-detection.md). For fresh ideas, this uses the design interaction pattern (token matching against idea prose). For WIP features, this uses file-based detection with design-pattern fallback.
4. **Load profile content.** For each active profile contributing a `design/` subdirectory, read its `index.md` and all always-load and matching conditional entries. These feed the refinement question pool and required design sections.
5. **Engage with subject matter.** Follow the selected process file's content-reading, refinement and drafting steps.
6. **Recommend next steps.** After drafting or substantive refinement, suggest an optional `$kk:clarify-docs` invocation naming the created or materially revised documents, before the `$kk:review-design` recommendation. An unchanged resume skips the clarification suggestion. Follow the selected process file for review recommendation and implementation recommendation.

Clarification is a separate user-selected editing workflow: this skill neither loads its procedure nor runs it automatically. Drafting still owns clear explanations and preservation of required sections, profile topics, decisions, task state and links. A clarification suggestion does not replace design review; neither recommendation executes a review or establishes independent verification.

## Ideas and Prototypes

_Use this to develop an idea into a written design/specification and implementation plan._

**For example:** Help me turn this idea into a written design, implementation plan, and task list before we start coding.

**Your job:** Help me turn it into a fully formed design, spec, implementation plan, and task list.

See [idea-process.md](./idea-process.md).

## Continue WIP Feature

_Use this to resume work on a feature that already has design docs and a task list in `/docs/feat/wip/`._

**For example:** Let's continue working on the auth system.

**Your job:** Review the current state of the feature, understand what's been done and what's next, then proceed with implementation.

See [existing-task-process.md](./existing-task-process.md).
Pliki w paczce (37)
  • SKILL.md 5 KB
  • example-tasks.md 4 KB
  • existing-task-process.md 3 KB
  • idea-process.md 17 KB
  • shared-capy-knowledge-protocol.md 2 KB
  • shared-idea-refinement-criteria.md 6 KB
  • shared-ideation-frameworks.md 6 KB
  • shared-profile-detection.md 9 KB
  • shared-verification-policy.md 3 KB
  • evals/clarity-after-drafting/README.md 1 KB
  • evals/clarity-after-drafting/eval.json 2 KB
  • evals/clarity-after-drafting/oracle/expected.json 4 KB
  • evals/clarity-after-drafting/oracle/runbook.md 3 KB
  • evals/clarity-after-drafting/test-files/accepted.md 1 KB
  • evals/clarity-refined-documents-only/README.md 1 KB
  • evals/clarity-refined-documents-only/eval.json 2 KB
  • evals/clarity-refined-documents-only/oracle/expected.json 3 KB
  • evals/clarity-refined-documents-only/test-files/docs/feat/wip/archive-label/design.md 1 KB
  • evals/clarity-refined-documents-only/test-files/docs/feat/wip/archive-label/implementation.md 1 KB
  • evals/clarity-refined-documents-only/test-files/docs/feat/wip/archive-label/tasks.md 1 KB
  • evals/clarity-unchanged-resume/README.md 1 KB
  • evals/clarity-unchanged-resume/eval.json 1 KB
  • evals/clarity-unchanged-resume/oracle/expected.json 3 KB
  • evals/clarity-unchanged-resume/test-files/docs/feat/wip/archive-label/design.md 1 KB
  • evals/clarity-unchanged-resume/test-files/docs/feat/wip/archive-label/implementation.md 1 KB
  • evals/clarity-unchanged-resume/test-files/docs/feat/wip/archive-label/tasks.md 1 KB
  • evals/hard-gate-enforcement/eval.json 1 KB
  • evals/hard-gate-enforcement/oracle/runbook.md 3 KB
  • evals/proportional-diverge-routing/eval.json 1 KB
  • evals/proportional-diverge-routing/oracle/runbook.md 3 KB
  • evals/review-design-catches-missing-sections/eval.json 1 KB
  • evals/review-design-catches-missing-sections/test-files/design.md 1 KB
  • evals/review-design-catches-missing-sections/test-files/tasks.md 1 KB
  • evals/wip-feature-no-subphases/eval.json 1 KB
  • evals/wip-feature-no-subphases/oracle/runbook.md 4 KB
  • evals/wip-feature-no-subphases/test-files/design.md 2 KB
  • evals/wip-feature-no-subphases/test-files/tasks.md 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · serpro69/claude-toolbox100Apache-2.0
cihantopac/markilo100Apache-2.0
NatikChhabra/claude-arsenal100MIT
AtlasScope/agent-kit100MIT
jeremylongshore/tons-of-skills-marketplace100MIT
NathanColosimo/skills100MIT
serpro69/claude-toolbox100Apache-2.0
ouestlabs/audio-ui100MIT
Vamp-pire/hype-me100MIT

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

  • 100workflow-prd-to-plan
    Zamienia PRD w szczegółowy plan wdrożenia z historyjkami użytkownika, zadaniami dla każdej warstwy i kryteriami akceptacji.
  • 100plan-feat
    Tworzy plany implementacji modułów nowej aplikacji w plikach markdown, po sprawdzeniu dokumentów względem kodu.
  • 100nixtla-prd-to-code
    Przekształca dokumenty PRD w wykonalne zadania implementacyjne z integracją TodoWrite i planami wdrożenia.
  • 100prd
    Generuje dokument wymagań produktowych (PRD) dla nowej funkcji, po którym opcjonalnie powstaje projekt techniczny (prd-to-spec) i zgłoszenia (to-issues).
  • 100feature
    Tworzy lekki Feature Brief (FEAT-NNN) dla drobnych i średnich funkcji produktowych, które nie wymagają pełnego PRD.
  • 100implementation-planner
    Zamienia PRD lub dokument wymagań w fazowy plan wdrożenia z plikami faz i zadań w katalogu .context/plans/ oraz porządkuje monolityczne dokumenty planistyczne.

Uwagi i zgłoszenia

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