Skip to content

nanaagyei/noetherkin / skills/task-assignment

task-assignment

Verified

Define a bounded, testable Noetherkin assignment and its investigation prompt without revealing the solution. Use when a learner requests next work or a manager recommends new scope; execution gates belong to team-lead.

FileKindSize
SKILL.mdskill md3.7 KB
assets/proposal.mdmarkdown2.0 KB
references/FOUNDATION_V1.mdmarkdown5.4 KB
references/OPEN_QUESTIONS.mdmarkdown3.5 KB
references/PROJECT_CHARTER.mdmarkdown6.4 KB
references/apprenticeship-config.schema.jsonconfig3.0 KB
references/architectural-invariants.mdmarkdown2.3 KB
references/assessment.schema.jsonconfig5.0 KB
references/assistance-model.mdmarkdown4.0 KB
references/attention-advisory.schema.jsonconfig3.8 KB
references/bundle.jsonconfig12.0 KB
references/cli.mdmarkdown18.6 KB
references/competencies.yamlconfig37.7 KB
references/competency-model.mdmarkdown5.0 KB
references/competency-state.schema.jsonconfig3.4 KB
references/conformance.mdmarkdown22.0 KB
references/contract-README.mdmarkdown6.9 KB
references/contract-manager.mdmarkdown2.4 KB
references/contract-task-assignment.mdmarkdown3.2 KB
references/contract-team-lead.mdmarkdown2.8 KB
references/current-project.schema.jsonconfig2.3 KB
references/current-track.schema.jsonconfig1.5 KB
references/evidence-model.mdmarkdown4.1 KB
references/evidence.schema.jsonconfig10.3 KB
references/forge.schema.jsonconfig9.5 KB
references/index.mdmarkdown3.6 KB
references/judgment-validity.mdmarkdown6.6 KB
references/learner-profile.schema.jsonconfig1.5 KB
references/leveling-framework.mdmarkdown3.4 KB
references/levels.yamlconfig8.0 KB
references/overview.mdmarkdown2.9 KB
references/permissions-model.mdmarkdown6.7 KB
references/project.schema.jsonconfig9.4 KB
references/proposals.mdmarkdown4.2 KB
references/review-model.mdmarkdown7.2 KB
references/review.schema.jsonconfig13.0 KB
references/runtime.mdmarkdown7.8 KB
references/selection-model.mdmarkdown6.1 KB
references/simulation-lifecycle.mdmarkdown8.0 KB
references/state-model.mdmarkdown13.7 KB
references/task.schema.jsonconfig13.8 KB
references/track.schema.jsonconfig1.3 KB

references/leveling-framework.md

View on GitHub
# Engineering levels

The exact behavioral expectations for all thirteen dimensions and six levels are in `catalog/levels.yaml`. These are internal simulator levels with no implied equivalence to employers, job titles, hiring assessments or credentials.

| Level | Scope anchor |
| --- | --- |
| E0 Apprentice | Guided bounded steps with explanations |
| E1 Junior Engineer | Independently verified localized changes |
| E2 Independent Engineer | Unfamiliar cross-component work |
| E3 Product Engineer | Product, library, model or tool outcomes through use |
| E4 Senior / Systems Engineer | Ambiguous systemic work and risk reduction |
| E5 Lead Engineer | Sustained practices and decisions across teams |

Expectations are observable behaviors rather than time served. They apply in the selected specialization and all core competencies. Production and collaboration behavior may be assessed in labeled simulation contexts, but cannot be represented as real employment or production experience. E5 simulated coordination must include attributable interactions and resulting artifacts; merely writing a leadership plan does not demonstrate its effects.

Promotion considers every next-level dimension explicitly and relates its cited evidence to core and selected specialization competencies. A narrow strength cannot substitute for missing ownership, testing or communication. More assistance changes the claim that can be made; independent work in an unrelated easy task cannot establish next-level scope. Effective level is derived from promotion decisions, never an average of competency levels. Only adjacent promotions are allowed; E5 is terminal for V1.

Use the [review protocol](review-model.md) for decision authority and outcome semantics. Task count, elapsed time, course completion, cloning and subjective encouragement cannot grant promotion.

## Domain-neutral equivalence and simulated effects

Product capability includes a library, command-line tool, offline model/evaluation pipeline or GPU kernel integrated into a usable system. Operation means reproducible release/use, observable failures, mitigation and sustained verification in the relevant environment; it does not require a network service. E3 debugging can concern interacting memory, numerical and throughput failures rather than cross-service requests. No core dimension may be waived as not applicable. E5 still requires demonstrated cross-team effects, with labeled simulation allowed.

For example, an offline inference-library progression may cover E1 local numerical regression, E2 unfamiliar kernel/dispatcher integration, E3 capability delivery with reproducible packages, resource/failure analysis and user-facing compatibility, E4 systemic portability/reliability improvements, and E5 independently observed adoption of validation/review practices across real or simulated teams. These are scope examples, not awarded levels; each still requires all dimensions, repeated independent evidence and adjacent review.

A simulated leadership effect requires actual learner interactions, resulting artifacts, an exercise constraint specified before the outcome by a separate reviewer, and a counterfactual or failure probe. Record the simulated setting and these artifact references in evidence fact/scope/rationale. A model narrating agreement, praise or adoption is not evidence of an effect. No simulation may be exported as real organizational experience.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall