Plan: Cataloguing all of OSRS into the progress tracker
Goal: turn the tracker from a hand-curated stub into a complete,
STATUS: EXECUTED — July 2026. Eleven parallel research agents swept the local OSRS Wiki mirror (
mcp/wiki-mcp, synced 2026-07-02) and wrote one fragment each intosrc/data/tracker/fragments/under the contract infragments/README.md. Result: 12 categories, ~620 items, ~2,260 sub-features (205 quests+miniquests, 63 bosses/raids, 115 slayer categories w/ 530+ monsters, 46 sailing islands, 61 minigames, all prayers/spells/ special attacks, every transport network, all 23 skills method-by-method). Existing implemented statuses were pinned in each brief and preserved. Maintenance = flip statuses in the fragments as content ships; the notes below on honesty rules still apply.
Goal: turn the tracker from a hand-curated stub into a complete, authoritative inventory of Old School RuneScape content — so the public tracker doubles as the project plan.
Why this shape
The site already renders Category → TrackedItem → SubFeature with computed
rollups. The research task is therefore pure data production: emit items in
that schema and the UI, percentages, and jump-nav all update for free.
The research pass (deep-research agents, one per domain)
Source of truth: OSRS Wiki only (project rule — data from Wiki/RuneLite, no third-party RSPS bases). Each agent sweeps its domain and emits a reviewed TypeScript fragment:
| Domain | Scope to enumerate | Est. items |
|---|---|---|
| Skills | 23 skills × training methods, tools, outfits, mechanics (already researched — 23 dossiers exist in the server repo at docs/docs/skills/) | ~400 sub-features |
| Quests | All quests (F2P + members), quest requirements graph, miniquests | ~180 |
| Minigames | All minigames + activities (Wiki "Minigames" category) | ~60 |
| Bosses & raids | Every boss, demi-boss, raid + per-boss mechanics list | ~70 |
| Achievement diaries | All regions × 4 tiers, per-task | ~12 areas |
| World systems | GE, banking, trading, clans, POH, farming patches/transport/teleport networks, shops | ~50 |
| Interfaces & QoL | Every game interface, settings, music, collection log, emotes | ~80 |
| Game modes | Ironman variants, Leagues, DMM, speedrunning worlds | ~10 |
Process per agent: sweep Wiki category pages → cross-check against a second
index (e.g. the Wiki's own navboxes) for completeness → emit
Category/TrackedItem fragments with everything planned → human review →
merge into progress.ts.
A final completeness-critic pass compares the merged result against the Wiki's top-level content portal to catch missed domains.
Keeping it honest after the import
- Statuses flow one way:
planned → in-progress → complete, andcompleterequires shipped + integration-tested + validated in-client. - Each server milestone PR should update
progress.ts+changelog.tsin the same change (or the landing repo gets a follow-up commit). - If the tracker outgrows one file, split into
src/data/progress/<category>.tsand re-export from an index — the schema doesn't change.
Possible later upgrades (not needed now)
- Generate parts of the tracker from the server repo itself (e.g. parse the content module tree) so "in progress" can't drift from reality.
- Per-item detail pages (
/progress/[category]/[item]) once items carry enough prose to justify them. - A JSON export endpoint so Discord bots / README badges can read the tracker.