compile-3d-workflow
/compile-3d-workflow
Na podstawie wywiadu wyznacza kierunek i kompilowalny przepływ pracy 3D, bez zdalnych, uwierzytelnionych, publikujących, wdrażających i nieodwracalnych zmian.
- Autor
- OutlineDriven ↗
- Repozytorium
- outline-driven-development ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 28.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 28.09.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Na podstawie wywiadu wyznacza kierunek i kompilowalny przepływ pracy 3D, bez zdalnych, uwierzytelnionych, publikujących, wdrażających i nieodwracalnych zmian.
Oryginalny opis (EN)
Use when the user asks for direction and a compilable 3D workflow from an interview. Not for remote, credential, publish, deploy, or irreversible changes.
Jak działa
- Contract
- Inputs
- Artifact schema
- Procedure
- Failure and recovery
- Output
Podgląd SKILL.md
---
name: compile-3d-workflow
description: 'Use when the user asks for direction and a compilable 3D workflow from an interview. Not for remote, credential, publish, deploy, or irreversible changes.'
---
# Compile 3D workflow
## Contract
| Field | Bound contract |
|---|---|
| Trigger | The user asks for direction and a compilable 3D workflow from an interview. |
| Authority | Reversible local: writes only the named local 3D workflow artifact file; rollback is deleting that file. No remote mutation. |
| Side effect | Writes one local 3D workflow artifact file. |
| Done | A validated local 3D workflow artifact file exists and passes every structural check. |
## Inputs
- A direction interview with the user, supplying: the problem being solved, what success looks like, binding constraints, and what is explicitly out of scope. All four required; none inferred.
- The output file path for the workflow artifact. Required.
## Artifact schema
The workflow artifact is a YAML file with this structure:
```yaml
problem: <string>
success_criteria: <string>
constraints: [<string>, ...]
out_of_scope: [<string>, ...]
topology:
nodes:
- id: <string>
task: <string>
depends_on: [<node_id>, ...]
ontology:
groups:
- name: <string>
members: [<node_id>, ...]
feedback_loops:
- name: <string>
sensor: <string>
comparator: <string>
actuator: <string>
```
Every node id referenced in `depends_on` must exist in `nodes`. Every node id in ontology group `members` must exist in `nodes`. Every feedback loop must name a sensor, comparator, and actuator as non-empty strings.
## Procedure
1. Conduct the direction interview. Ask the user for the problem, success criteria, binding constraints, and explicit out-of-scope. Record the answers verbatim. Done when: all four interview inputs are recorded verbatim, or the missing input is named and the skill stops.
2. Author the workflow artifact from the interview answers. Build the three dimensions:
- Topology: a DAG of tasks. Each node has an id, a task description, and a depends_on list naming the node ids it waits on. No cycles. No node depends on itself. Every depends_on entry must reference an existing node id.
- Ontology groups: named concept clusters classifying the work domains. Each group names its member node ids. Every group is non-empty. Every member must exist in the topology.
- Feedback loops: cybernetic control cycles. Each loop names its sensor (what is measured), comparator (what is expected), and actuator (what action re-routes). All three are non-empty strings.
Done when: the artifact combines all three dimensions from the interview answers.
3. Validate the artifact against the schema. Check every rule:
- Every node has a unique id and a non-empty task.
- Every depends_on entry references an existing node id.
- No cycle exists in the dependency graph (topological sort succeeds).
- Every ontology group is non-empty and every member references an existing node id.
- Every feedback loop names a non-empty sensor, comparator, and actuator.
Done when: every check passes, or the specific defect is named and the skill stops.
4. Write the validated artifact to the output file path as YAML. State the rollback path: delete the local artifact file. No remote state was touched. Done when: the artifact file is written and the rollback path is stated.
## Failure and recovery
- Interview incomplete: if the user cannot supply the problem, success criteria, constraints, or scope, stop and report which inputs are missing. Do not infer or fabricate direction.
- Schema validation failure: if any node lacks dependencies, any ontology group is empty, any feedback loop is missing its sensor, comparator, or actuator, any depends_on entry references a non-existent node, or a cycle exists in the dependency graph, report the specific defect and stop. Do not emit a partial artifact as complete.
- Partial-result rule: a partially written artifact file is not a compiled workflow. Delete it and report the rollback.
## Output
A validated local 3D workflow artifact file (YAML) containing the DAG topology, ontology groups, and feedback loops, with every structural check passing.
Pliki w paczce (2)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · OutlineDriven/outline-driven-development | 100 | Apache-2.0 |
| gosuda/dalcom-skills | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 0861994a2ae7 (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
- 90create-branch
Tworzy nową gałąź git i rozpoczyna na niej pracę, bez zmian zdalnych, poświadczeń i nieodwracalnych. - 90automatic-freeform-graphs-design
Tworzy luźniejszy graf koncepcyjny do pracy eksploracyjnej, bez zmian zdalnych, poświadczeń, publikacji, wdrożeń ani nieodwracalnych. - 90deep-research
Przygotowuje gruntowny raport ze źródłami na zadany temat, bez zdalnych ani nieodwracalnych zmian. - 100append-run-log
Zapisuje zakończony przebieg agenta jako trwały, przeszukiwalny dowód, bez zdalnych i nieodwracalnych zmian w systemach. - 90brand-authority
Pilnuje, by wynik zgodny z marką i stylem był spójny, bez publikowania, wdrażania i zmian nieodwracalnych.