alphazede
- 16 skills
- 0 followers
- 6 hours ago last updated
- ▌ Scribe · alphazedeTranscribe Journey decisions, authority events, ledger snapshots, and lineup selections as an event side lane. Use for Scribe. Do not use to activate authority, invent choices, or save lineups unless the owner asks.
- ▌ Crewmate · alphazedeImplement one approved bounded packet in an exact write set. Continue the same-wave session when identity, authority, route, and generation are unchanged. Use for Crewmate, implementation, repair, or integration packets. Do not use for orchestration, planning, independent assurance, publication, destructive action, owner decisions, or unset scope.
- ▌ Explorer · alphazedeOwn one approved execution wave, continuing bounded packets when the envelope is unchanged and integrating their evidence. Use for Explorer Journey, wave orchestration, proven-independent in-wave lanes, or parallel packet sequencing. Do not use for implementation, cross-wave work, planning, automatic nesting, or independent assurance.
- ▌ Surveyor · alphazedeIndependently compare one stable integrated candidate with the approved user-facing outcome in a fresh session at the end. Use for Surveyor or outcome acceptance. Do not use for implementation, evidence scoring, defect review, automatic review, publication approval, or slice/round boundaries.
- ▌ Navigator · alphazedeCompatibility diagnostic for plans that still name Navigator. Use when an existing plan assigns Navigator or asks to sequence expedition waves as navigator. Do not use for new Journeys, packet work, planning, assurance, or publication.
- ▌ Validator · alphazede bundleCompatibility diagnostic for plans that still name Validator. Use when an existing plan assigns Validator. Do not use for new Journeys, evidence validation, or as an active assurance role.
- ▌ Park Ranger · alphazedeIndependently review one exact stable candidate for introduced actionable defects in a fresh session at the end. Use for Park Ranger, code review, or defect adjudication. Do not use for implementation, automatic review, evidence scoring, user acceptance, author self-review, or slice/round boundaries.
- ▌ Bearing Lite · alphazede bundleBearing Lite Router for Journeys. Not for ordinary work, assigned packets, implementation, or publication.
- ▌ Set Bearings · alphazedeCreate or resume the visible Journey workspace and bounded repository map after Repository Fit is confirmed. Use for Set Bearings or stale project context. Do not use before fit, for owner decisions, design, implementation, hidden state, or deleting historical plans.
- ▌ Map The Route · alphazede bundleCreate or resume Bearing's complete five-artifact planning package after material decisions are settled. Use for Map the Route or missing planning artifacts. Do not use to implement, select models, self-approve, or bypass the single integrated owner review.
- ▌ Test Engineer · alphazedeOne Test Engineer role with Planning and Assurance sessions. Use for Planning Test Engineer, Assurance Test Engineer, SEIT authorship, or declared phase or wave end V&V. Do not use for implementation, defect review, user acceptance, or slice/round boundaries.
- ▌ Repository Fit · alphazedeVerify and propose one target repository and plan directory when repository identity is absent or ambiguous. Use for Repository Fit before Set Bearings. Do not use after owner-confirmed fit, for parent-wide exploration, planning decisions, product edits, role routing, or publication.
- ▌ Gather Supplies · alphazedeRelentlessly resolve material owner decisions for a Bearing Journey, one dependency-ordered question at a time, until shared understanding is explicit. Use for Gather Supplies or unresolved plan intent. Do not use for discoverable repository facts, design drafting, implementation, or settled decisions.
- ▌ Plan Integrator · alphazedeReconcile specialist outputs and generate implementation.json and review.html. Use for Plan Integrator. Do not invent owner intent, requirements, models, or V&V, or author V&V.
- ▌ Systems Modeler · alphazedeSelect modeling mode and attach view metadata after Requirements Engineer work and before design finalization. Use for Systems Modeler. Do not finalize requirement mappings against unstable requirements.
- ▌ Integration Engineer · alphazedeDual-session Integration Engineer for planning assembly strategy and execution assembly of the exact integrated candidate. Use for Planning Integration Engineer or Execution Integration Engineer. Do not implement missing product behavior or self-certify.