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/levels.yaml

View on GitHub
{
  "schema_version": "2.0",
  "catalog_version": "2.0",
  "scope": "Internal simulator levels; no employer or credential equivalence.",
  "dimensions": [
    "independence",
    "scope",
    "ambiguity",
    "codebase_navigation",
    "implementation",
    "debugging",
    "testing",
    "design",
    "systems_thinking",
    "production_engineering",
    "ownership",
    "technical_communication",
    "collaboration"
  ],
  "levels": [
    {
      "id": "E0",
      "name": "Apprentice",
      "expectations": {
        "independence": "Works through a bounded step with guidance and explains it back.",
        "scope": "Changes one small function or document with clear boundaries.",
        "ambiguity": "Identifies missing information in an explicit assignment.",
        "codebase_navigation": "Locates an entry point using documentation and guided search.",
        "implementation": "Makes a small change and explains each affected line.",
        "debugging": "Reads errors and logs with guidance and reproduces a symptom.",
        "testing": "Runs a provided test and explains the expected assertion.",
        "design": "Explains an existing design choice and one alternative with help.",
        "systems_thinking": "Draws a basic input-to-output path.",
        "production_engineering": "Runs locally with guidance and distinguishes simulation from production.",
        "ownership": "Reports a blocker and preserves investigation notes.",
        "technical_communication": "Describes an observation separately from a guess.",
        "collaboration": "Asks focused questions and responds to review feedback."
      }
    },
    {
      "id": "E1",
      "name": "Junior Engineer",
      "expectations": {
        "independence": "Completes bounded work independently and asks for help at identified limits.",
        "scope": "Owns a localized component change.",
        "ambiguity": "Clarifies acceptance criteria before coding.",
        "codebase_navigation": "Traces a local call path and finds related tests independently.",
        "implementation": "Implements localized behavior with errors and edge cases.",
        "debugging": "Diagnoses localized defects independently.",
        "testing": "Adds regression tests that fail for the original defect.",
        "design": "Chooses a local interface and explains a concrete alternative.",
        "systems_thinking": "Explains dependencies and local failure propagation.",
        "production_engineering": "Uses logs and follows a documented nonproduction release procedure.",
        "ownership": "Follows a small task through review and verification.",
        "technical_communication": "Writes a reproducible bug report and clear change rationale.",
        "collaboration": "Incorporates feedback and reviews a bounded change constructively."
      }
    },
    {
      "id": "E2",
      "name": "Independent Engineer",
      "expectations": {
        "independence": "Plans unfamiliar work and uses limited targeted assistance.",
        "scope": "Owns a change across multiple components.",
        "ambiguity": "Turns an underspecified problem into testable requirements.",
        "codebase_navigation": "Maps unfamiliar component interactions from source.",
        "implementation": "Integrates cross-component changes with compatibility handling.",
        "debugging": "Tests hypotheses for unfamiliar cross-component failures.",
        "testing": "Chooses unit and integration coverage based on failure boundaries.",
        "design": "Defends API and data choices using constraints and alternatives.",
        "systems_thinking": "Explains consistency and dependency failure effects in the affected path.",
        "production_engineering": "Validates release readiness, rollback and useful telemetry in a safe environment.",
        "ownership": "Closes cross-component work and identifies remaining operational risks.",
        "technical_communication": "Explains tradeoffs and uncertainty to technical and nontechnical readers.",
        "collaboration": "Coordinates dependencies and provides evidence-based peer review."
      }
    },
    {
      "id": "E3",
      "name": "Product Engineer",
      "expectations": {
        "independence": "Drives product outcomes and identifies when specialist input is needed.",
        "scope": "Owns a product, library, model or tool capability through sustained use.",
        "ambiguity": "Reconciles competing user needs into a scoped delivery plan.",
        "codebase_navigation": "Maps component boundaries and ownership across a complete capability.",
        "implementation": "Delivers integrated behavior with compatibility, reproducibility and operational controls.",
        "debugging": "Diagnoses interacting correctness, concurrency or performance failures across component boundaries.",
        "testing": "Validates end-to-end behavior including degraded dependencies.",
        "design": "Balances user needs, reliability and delivery cost in capability design.",
        "systems_thinking": "Analyzes resource limits, recovery and data flow across interacting components.",
        "production_engineering": "Handles a safely scoped incident exercise and verifies mitigation effects.",
        "ownership": "Tracks impact after delivery and follows up on defects.",
        "technical_communication": "Communicates incident impact and decisions with explicit evidence limits.",
        "collaboration": "Coordinates reviews and negotiates component interfaces and usage contracts with peers."
      }
    },
    {
      "id": "E4",
      "name": "Senior / Systems Engineer",
      "expectations": {
        "independence": "Leads ambiguous work while creating space for others to decide.",
        "scope": "Owns systemic changes across interacting subsystems or engineering workflows.",
        "ambiguity": "Frames an unclear systemic problem and tests competing explanations.",
        "codebase_navigation": "Finds architectural contributors across unfamiliar subsystems.",
        "implementation": "Stages risky systemic changes with rollback and compatibility strategy.",
        "debugging": "Leads ambiguous investigations and identifies architectural contributors.",
        "testing": "Designs failure experiments that expose systemic risks.",
        "design": "Designs evolutionary architecture and defends long-term tradeoffs.",
        "systems_thinking": "Models capacity, failure domains and coupled system behavior.",
        "production_engineering": "Improves reliability using incident and measurement evidence.",
        "ownership": "Owns systemic risk reduction and verifies sustained improvement.",
        "technical_communication": "Writes architecture proposals with alternatives, risks and evidence.",
        "collaboration": "Mentors independent decision-making and resolves technical disagreement."
      }
    },
    {
      "id": "E5",
      "name": "Lead Engineer",
      "expectations": {
        "independence": "Enables independent engineering decisions across teams.",
        "scope": "Improves engineering practices spanning multiple teams.",
        "ambiguity": "Aligns conflicting system and organizational constraints.",
        "codebase_navigation": "Creates shared maps and practices that let others navigate systems.",
        "implementation": "Guides multi-team execution with explicit contracts and verifies outcomes.",
        "debugging": "Improves shared debugging, observability and incident-learning practices.",
        "testing": "Establishes risk-based validation practices and checks their effectiveness.",
        "design": "Guides architectural direction through explicit decision principles.",
        "systems_thinking": "Anticipates cross-team systemic risks and coordinates mitigation.",
        "production_engineering": "Improves operational readiness across teams with observable outcomes.",
        "ownership": "Sustains cross-team technical stewardship and develops new owners.",
        "technical_communication": "Builds shared understanding of strategy and its measurable limits.",
        "collaboration": "Develops reviewers and facilitates accountable cross-team decisions."
      }
    }
  ]
}
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