common-operator-profile
/common-operator-profile
Ocenia biegłość techniczną użytkownika na podstawie treści wiadomości i dostosowuje język wyników w przepływach SDLC.
- Autor
- HoangNguyen0403 ↗
- Repozytorium
- agent-skills-standard ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.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 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Ocenia biegłość techniczną użytkownika na podstawie treści wiadomości i dostosowuje język wyników w przepływach SDLC.
Oryginalny opis (EN)
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
Jak działa
- Priority: P0 (CRITICAL)
- 1. Infer, Never Ask
- 2. Register Rules Per Tier
- 3. Proxy-Defaults Rule
- Anti-Patterns
- Blocked-request wording
Podgląd SKILL.md
---
name: common-operator-profile
description: Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
metadata:
triggers:
files: []
keywords:
- operator profile
- audience adaptation
- non-technical stakeholder
- business owner
- plain language summary
---
# Operator Profile
## **Priority: P0 (CRITICAL)**
## 1. Infer, Never Ask
Classify the requesting operator into exactly one tier from message content alone. Do not ask "how technical are you?" or similar — inference only. Treat the tier as internal response context: continue with the requested work in that register. Never return only `business`, `hybrid`, or `technical` as the answer.
| Tier | Signal |
| --- | --- |
| `technical` | Names files, branches, PRs, diffs, frameworks, stack traces, ticket IDs, or existing code. |
| `hybrid` | Fluent in one stack, asks definitional questions about another ("I know Laravel, new to NestJS"). |
| `business` | Outcome/goal language only, no code or file artifacts, business vocabulary ("customers", "revenue", "an app that tracks..."). |
Default to `hybrid` when ambiguous. Revise silently as new evidence arrives in the same session; never re-ask. The profile is decided once per session and carried forward as `operator_profile` in every Handoff Payload so downstream workflows never re-infer it.
An explicit `profile=business|hybrid|technical` invocation argument always overrides inference.
For traceable workflow output, name the inferred register once when it matters (for example, `Profile: business` or `Profile: technical`) and then continue with the substantive answer. Never return only the label. File paths, requirement IDs, and test references such as `prd-checkout.md` and `checkout.spec.ts` are technical signals even when the request is otherwise brief.
## 2. Register Rules Per Tier
- **`business`**: Lead every response with a plain-language outcome summary (what changes for the business, no jargon). Move file paths, IDs, commands, and stack detail into a trailing "Technical Appendix" the operator can skip. Frame Blocking Questions as business choices, each with a recommended default answerable by "go with your suggestion." Proxy purely technical decisions (tech stack internals, library choice) without asking — record them as assumptions, not blockers.
- **`hybrid`**: Full technical detail. Define unfamiliar-stack concepts on first use and map them to the operator's declared home stack when known (e.g., map a NestJS `Module` or `Provider` to its Laravel equivalent).
- **`technical`**: Terse, full detail, no explanations of standard concepts. If essential artifacts are unavailable, name the exact supplied requirement, file, or test needed; do not replace the task response with a profile label.
## 3. Proxy-Defaults Rule
For `operator_profile=business`, workflows with a hard-blocking floor (missing sponsor, missing SMART metric, missing scope fence) must draft a sensible default for each missing item and present them as one confirm-with-default question round instead of returning BLOCKED outright. Only return BLOCKED if the operator rejects the drafted defaults or the workflow cannot obtain operator confirmation.
Use the literal label `SMART metric` when drafting the measurable success target, and use `Profile: technical` when file, requirement, or test references establish a technical operator.
## Anti-Patterns
- **No upfront skill-level question**: never ask the operator to self-classify.
- **No persisted profile config**: infer per-session from the message; do not read or write a stored preference file.
- **No jargon-first response for `business` tier**: leading with file paths or command output before the plain-language summary is a violation.
## Blocked-request wording
- If implementation cannot proceed, say clearly that you are unable to implement because required access or inputs were not supplied; do not invent evidence.
- Continue independent safe analysis with explicit assumptions when artifacts are unavailable; do not implement work missing required inputs.
Pliki w paczce (2)
- LICENSE 1 KB
- SKILL.md 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · HoangNguyen0403/agent-skills-standard | 100 | MIT |
| HoangNguyen0403/agent-skills-standard | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 59332717e5c1 (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
- 100common-decision-discipline
Dobiera głębokość analizy decyzji w cyklu SDLC, zapisuje ślad dowodów, opcje i przegląd przed zatwierdzeniem. - 100sdlc-readiness-review
Ocenia gotowość materiałów SDLC, specyfikacji i przekazań do bramki gotowości i wydaje werdykt. - 90impact-work-sdlc
Prowadzi projekt od krótkiego briefu biznesowego do zaakceptowanej i scalonej pracy, z bramkami i wznowieniem. - 100sdlc-router
Decyduje, czy praca wymaga SDLC lub ADS i jakie minimalne materiały są w niej uzasadnione. - 90sdlc-plan
Zamienia zatwierdzoną specyfikację w plan techniczny z punktami styku, ryzykiem, alternatywami, strategią testów i wdrożenia. - 95sdlc-conventions
Określa wspólne zasady wtyczki sdlc-loop: układ katalogów pracy, plik status.json, łańcuch plików i bramki akceptacji dla etapów.