Zarządzanie i produkt · Planowanie
autoplan
/autoplan
Pisze plan wdrożenia bez zatrzymywania się na pytania, gdy użytkownik o to prosi.
Dla kogo
- Autor
- prathamdby ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.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
- 8
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 10.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
Pisze plan wdrożenia bez zatrzymywania się na pytania, gdy użytkownik o to prosi.
Oryginalny opis (EN)
When the user wants an implementation plan written without stopping for questions.
Jak działa
- Options and triage
- 1. Evidence
- 2. Lenses
- 3. Plan
Sekcje z nagłówków SKILL.md, w oryginale · 81 linii, 585 słów
Podgląd SKILL.md
--- name: autoplan description: > When the user wants an implementation plan written without stopping for questions. --- # Autoplan Analysis only. Deliver one plan in thread, or at the caller's named path. ## Options and triage Default: current repo, standard depth, thread output. Quick/sketch uses Shape and Risks with always-on lenses. Thorough/risky/migration uses deep, winning over quick; a named area scopes evidence. Resolve conflicting scope narrowly and record both readings under Assumptions; never ask. Before evidence, `BLOCKED` if no groundable verb/object/area, a non-repo intent has no plannable target, or building rather than planning was requested. Name the missing piece and one workable example; emit no lenses/map/milestones on refusal. A build request does not authorize product edits by this skill. Trivial means one module, no contract/data/signature change, and one-sentence behavior. Return `DIRECT` plus that sentence and three lines: shape, files, first step; no lenses. Otherwise record `intent | scope | depth | terminal`. Done when triage has a terminal or a grounded target. ## 1. Evidence Check whether the requested contract already exists; harden an existing match, not rebuild it. Locate sibling recon's installed `SKILL.md` to resolve its anchor and shared/legacy memory rules. Read a repository-verified snapshot whose head resolves; do not invoke a refresh merely to read it. Without usable memory, cold-scan at most three anchors for each of at most 30 manifest modules. Missing recon is not an evidence dependency: use that bounded scan instead. Scan ADR trees (`docs/adr/`, `adr/`, `doc/adr/`, `docs/decisions/`) silently when absent. Note TODOs, recent reverts, and duplication. Dirty content is an Assumptions overlay, not proof of existing contracts. Every later claim cites a path/test/ADR, a scoped no-match result, or an explicit missing-evidence Assumption; cite inherited patterns. Done when material claims have provenance. ## 2. Lenses Apply all always-on probes in `REFERENCE.md`: contracts/API, failure/rollback, longevity/debt. For a leaf, playbook, or matcher, also apply `references/router-contracts.md`. Score every probe for each activated lens, turning a hit into a cited risk owned by a plan step; close each lens pass with cite, risk → step, or no evidence. Deep activates all. Otherwise load only triggered lenses: - Schema/backfill, stored artifacts, toolchain: `references/data.md`. - External consumers/stored payloads: `references/compatibility.md`. - Auth/secrets/PII/untrusted input: `references/security.md`. - Hot paths/cost-bearing calls: `references/cost.md`. - Services/deployment/paging: `references/operations.md`. State one skip line per inactive lens. Done when every active probe is scored and each risk has an owner. ## 3. Plan Specify decisions, changed contracts, constraints, and deviations from cited patterns, not implementation bodies or restatements. Standard/deep includes: Assumptions; Shape (bold sentence + pattern); Layer map (NEW/CHANGED roles); phase sequence; file-plus-symbol grounding (prose: file + contract step); worst-first Risks (probability × impact, or stated judgment); Milestones; non-goals. Sketch includes only Shape and Risks. Small work is one PR. Larger work lists every milestone in build order, and each milestone is one reviewable vertical PR. Approval covers that whole list, in that order. The first milestone is the thinnest end-to-end contract/check slice. Later milestones stay in the same approval. Do not ask which milestone to build. Name landed symbols, expected success and relevant failure outcomes, and assertions or observed manual results proving them. Exit zero alone is not proof. End the plan on its last section. End a DIRECT reply on its three lines. End a BLOCKED reply on the missing piece and the workable example. Add no next step, handoff, review route, or ship route in any section. A route the caller already has stays with the caller. Name a skill or file when the work changes it. Done with `PLANNED` when behavior is grounded or assumed, risks are owned, and every milestone has outcome-linked checks. Terminals: `PLANNED`, `DIRECT`, `BLOCKED`.
Pliki w paczce (8)
- REFERENCE.md 1 KB
- SKILL.md 4 KB
- references/compatibility.md 1 KB
- references/cost.md 1 KB
- references/data.md 1 KB
- references/operations.md 1 KB
- references/router-contracts.md 1 KB
- references/security.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · prathamdby/skills | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| shaunjones-gh/lilystack | 100 | MIT |
| frankxai/agentic-creator-os | 95 | Apache-2.0 |
| frankxai/agentic-creator-os | 90 | Apache-2.0 |
| OutlineDriven/outline-driven-development | 90 | Apache-2.0 |
| gosuda/dalcom-skills | 85 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 364b9f72e1b4 (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
- 100trove-autoplan
Zamienia pomysł w plan wdrożenia, składając kolejno specyfikację, historyjki użytkownika i podgląd notatek o wydaniu. - 90autoplan-and-autopilot
Przegląda plan z czterech perspektyw, układa listę zadań i wykonuje lokalne, odwracalne kroki przy kontrolowanych bramkach. - 100autopilot
Prowadzi zatwierdzony plan dostawy przez bramki faz, od zatwierdzenia po wykonanie całego łańcucha. - 90create-plan
Przeprowadza wywiad z użytkownikiem i pisze plan wdrożenia dla bieżącej prośby o funkcję. - 81deep-plan
Pisze lub poprawia plan wdrożenia dla zatwierdzonego celu deep-work, zanim rozpocznie się implementacja. - 100create-plan
Tworzy plik .plan.md, gdy użytkownik prosi o przygotowanie lub napisanie planu.