Przejdź do treści
Biblioteka skilli
Programowanie · Planowanie

isolating-development-work

/isolating-development-work

Izoluje prace deweloperskie na etapie planowania tak, by wynik dało się prześledzić, niezależnie zrecenzować i bezpiecznie przekazać innemu agentowi.

Repozytorium
forge-os ↗
Licencja
MIT
Ostatnia zmiana repozytorium
01.08.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
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Izoluje prace deweloperskie na etapie planowania tak, by wynik dało się prześledzić, niezależnie zrecenzować i bezpiecznie przekazać innemu agentowi.

Oryginalny opis (EN)

Use when isolating development work is required during planning work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.

Jak działa

  1. Overview
  2. Trigger
  3. Required Inputs
  4. Method-Specific Protocol
  5. Procedure
  6. Verification Questions
  7. Evidence Packet
  8. Output Contract
  9. Quality Gate
  10. Forbidden Shortcuts
Sekcje z nagłówków SKILL.md, w oryginale · 125 linii, 947 słów
Podgląd SKILL.md
---
name: isolating-development-work
description: "Use when isolating development work is required during planning work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent."
license: MIT
compatibility: "ForgeOS-compatible Agent Skills hosts; no provider-specific model required."
metadata:
  author: forgeos-community
  version: "0.2.0"
  pack: planning
  kind: core
  status: candidate
---

# Isolating Development Work

## Overview

This skill owns one bounded responsibility: **isolating development work**. Its focus is isolating development work within planning lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope.

## Trigger

Activate only when the project is in one of these stages: `planning`, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request.

## Required Inputs

- `architecture-decision`
- `threat-model`
- Optional: `product-definition`
- Optional: `domain-blueprint`
- Current gate result, open findings, artifact hashes, and invalidation state
- Required tools: none
- Optional tools: none
- Confirmed human decisions relevant to this scope

## Method-Specific Protocol

1. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by isolating development work.
2. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to isolating development work.
3. Apply isolating development work only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
4. Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
5. Create reproducible checks that would fail if isolating development work were incomplete or implemented incorrectly.

## Procedure

1. Read verified artifacts and acceptance contracts.
2. Slice work into independently reviewable vertical increments.
3. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by isolating development work.
4. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to isolating development work.
5. Apply isolating development work only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
6. Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
7. Create reproducible checks that would fail if isolating development work were incomplete or implemented incorrectly.
8. Declare exact files, interfaces, dependencies, and test commands.
9. Sequence tasks by dependency and risk, not convenience.
10. Attach a reviewer gate and evidence requirement to every task.
11. Publish an executable plan with no placeholders.

## Verification Questions

- Does the artifact make the owned decision for isolating development work explicit and bounded?
- Are failure, recovery, permissions, concurrency, and irreversible side effects addressed where applicable?
- Can every load-bearing claim be traced to a confirmed fact, direct artifact, executable check, or declared assumption?
- Would a downstream agent know exactly what changed, what remains open, and what must be invalidated?

## Evidence Packet

Produce or reference all applicable evidence:

- `isolating-development-work-decision-table`
- `isolating-development-work-verification-report`
- `isolating-development-work-handoff-envelope`

Evidence must identify the current artifact hash, command or method used, result, reviewer identity, timestamp, and limitations.

## Output Contract

Produce:
- `execution-plan`
- `acceptance-contracts`

The primary artifact must include schema version, provenance, consumed artifact IDs, decisions, evidence references, residual risks, validation state, and invalidation targets. Narrative explanation may accompany the artifact but cannot replace it.

## Quality Gate

Reviewer: `independent-reviewer`

- The output directly and completely performs isolating development work within its declared boundary.
- Does the artifact make the owned decision for isolating development work explicit and bounded?
- Are failure, recovery, permissions, concurrency, and irreversible side effects addressed where applicable?
- Can every load-bearing claim be traced to a confirmed fact, direct artifact, executable check, or declared assumption?
- Would a downstream agent know exactly what changed, what remains open, and what must be invalidated?
- Every material claim is traceable to an input, decision, executable check, or evidence item.
- Required fields are complete and machine-readable.
- The producing agent is not the approving reviewer.
- Open uncertainty and residual risk are explicit; critical findings are never hidden by an aggregate score.

Pass only when: All mandatory rules pass, evidence targets the current artifact hash, and no unresolved critical finding applies.

## Forbidden Shortcuts

- Do not infer a material requirement that the user has not confirmed.
- Do not replace a typed artifact with a long explanation.
- Do not approve work produced by the same agent identity.
- Do not hide a critical failure behind a high aggregate score.
- Do not load unrelated project history, files, references, or skill bodies.
- Do not mark evidence complete when it targets a different artifact hash or version.

## Failure Modes

- guessing a material requirement
- producing prose without the contracted artifact
- self-approving the output
- expanding scope without a decision record
- treating isolating development work as a naming exercise
- covering only the happy path
- creating extension points without a current contract or consumer

## Escalation and Invalidation

Stop and request a human decision when scope, risk acceptance, irreversible action, cost ceiling, privacy boundary, or product direction is materially ambiguous. When this artifact changes, invalidate only descendants named by the artifact graph; preserve unaffected verified branches.

## Handoff

- Next transition: the graph router selects a real consumer of `execution-plan`, `acceptance-contracts`.
- Required evidence: `contract-validation`, `independent-review`, `isolating-development-work-decision-table`, `isolating-development-work-verification-report`, `isolating-development-work-handoff-envelope`.
- Required envelope fields: `artifactId`, `schemaVersion`, `sha256`, `producingSkill`, `producingAgent`, `consumedArtifacts`, `decisionIds`, `evidenceIds`, `residualRisks`, `validationState`, `invalidationTargets`, `stopCondition`.
- Stop condition: Output contract is satisfied, a blocker is recorded, or a material human decision is required.

## Token and Context Policy

Load at most 8 direct artifacts and reference depth 1. Use stable IDs, hashes, signatures, and deltas instead of repeating full history. Use established domain terminology, state each requirement once, and spend context on decisions, code, tests, or evidence rather than narration.

## Reference Playbook

Load [skills/references/core/planning.md](../../../references/core/planning.md) only when this skill needs pack-wide decision tables, evidence patterns, or cross-skill handoff rules.

See `contract.json` for the machine-readable contract.
Pliki w paczce (2)
  • SKILL.md 7 KB
  • contract.json 6 KB

Wersje

W bazie nie ma innych skilli o nazwie isolating-development-work.

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

  • 90managing-change-impact
    Zarządza wpływem zmian na etapie planowania tak, by wynik dało się prześledzić, niezależnie zrecenzować i bezpiecznie przekazać innemu agentowi.
  • 90managing-software-dependencies
    Prowadzi zarządzanie zależnościami oprogramowania tak, by wynik dało się prześledzić, niezależnie zrecenzować i bezpiecznie przekazać innemu agentowi.

Uwagi i zgłoszenia

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