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/architectural-invariants.md

View on GitHub
# Architectural invariants

| ID | Requirement | Violation example |
| --- | --- | --- |
| INV-001 | Learner is default code author | Completing assigned code before the learner attempts it |
| INV-002 | Formal evaluation requires relevant evidence | Promoting from conversational impressions |
| INV-003 | No role fabricates state | Reporting a test passed without a run |
| INV-004 | Source and simulator state remain separable | Requiring upstream to vendor learner records |
| INV-005 | Promotion is demonstrated competency based | Promoting after ten tickets |
| INV-006 | Core skills require no model vendor | A protocol field requiring a proprietary thread ID |
| INV-007 | Assistance is attributable where practical, otherwise unknown | Recording undocumented help as independent |
| INV-008 | Upstream policies constrain simulator actions | Sending an unauthorized contribution |
| INV-009 | Each critical fact has one canonical source | Editable level in both profile and review chain |
| INV-010 | Implementation help is progressively disclosed | Giving full code at the first hint request |
| INV-011 | Formal records are immutable with explicit corrections | Deleting contrary evidence |
| INV-012 | Fixture and live provenance never mix | Using a demo review for a live promotion |
| INV-013 | Roles and skill capabilities are separate | A manager loading code-review to gain promotion rights |
| INV-014 | Consequential writes require structural and semantic validation | Accepting an unresolved evidence ID |
| INV-015 | External/destructive actions require explicit authorization | Automatically pushing a learner branch |
| INV-016 | Unknown facts remain unknown | Inferring successful deployment from a config file |
| INV-017 | Promotion has separate technical and decision authority | Team lead acting as the only formal reviewer |
| INV-018 | No partial transaction is reported successful | Updating completion while losing its evidence |
| INV-019 | Tracks are advisory and do not own skills or evidence | Treating an advanced recommendation as a promotion gate |
| INV-020 | Scope changes are explicit and prospective | Rewriting historical reviews when a learner switches tracks |

The conformance scenarios exercise these invariants. An implementation must preserve them even when its agent instructions, prompt or UI differs.
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: 471kUpdated 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