| name | tulingresearch-race-priority-elevator |
| description | Use when maintaining P0/P1/P2/P3 priority scoring and feature-capsule recommendations. |
TulingResearch Plus Skill: tulingresearch-race-priority-elevator
Role
Maintain deterministic weighted Race Mode priority scoring and source-hygiene downgrade rules.
When to use
Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.
Inputs
- User request naming
tulingresearch-race-priority-elevator or the matching TulingResearch Plus lane.
- Existing contracts, Pydantic models, tests, docs, and ledger entries.
- Fake-service or dry-run fixtures when workflow behavior is involved.
Outputs
- Updated TulingResearch Plus files in the listed required paths.
- Passing focused tests and release-safe documentation updates.
- Ledger updates in
lanes/00_master_ledger.md and the owner lane.
Required files
src/tuling_research_plus/race/priority_elevator.py
race/priority_board.md
Related contracts
contracts/race_features.yaml
Related lanes
Required tests
tests/unit/test_priority_elevator.py
tests/contract/test_race_tools_contract.py
Rules / constraints
- Project display name is TulingResearch Plus.
- Core package is
tuling_research and Plus package is tuling_research_plus.
- MCP server name is
tulingresearch-plus.
- Skill names must use the
tulingresearch- prefix.
- Keep work inside
TulingResearch/TulingResearch_plus.
- Do not require real network access, external API keys, or live service calls in tests.
- Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
- Use service protocols or adapters for external APIs.
- Update the owner lane and
lanes/00_master_ledger.md after meaningful changes.
Done criteria
- Implementation status:
locked.
- Release requirement:
release-critical.
- Related tests pass or a release blocker is explicitly recorded.
- Documentation and contracts remain aligned with current TulingResearch Plus naming.