Loading…
Scope
Generated 01/06/2026
Paste this into Claude Code (or any coding agent). It saves the spec to SCOPE.md and builds from it — no extra prompting.
I'm starting a new build — an internal tool for Ensign Software. I've already scoped it; the full specification is published as markdown at the URL below. Pull it into the project as a file and build from it.
Save the spec locally:
curl -fsSL "https://ensign-scope.jg-toolbox.xyz/s/b98ceb1a3040c11bec186357d576f03d" -o SCOPE.md
Then read SCOPE.md — it has the overview, data model, pages, non-functional requirements, and an ordered task list. Build it:
1. Scaffold the project per the spec (the stack it implies, the data model, the pages).
2. Write a project CLAUDE.md from the scaffolded code + the spec as you go.
3. Resolve the spec's open questions, or record the assumptions you make.
4. Work the tasks in milestone order, verifying (typecheck/lint/build) at each step.
The spec is the source of truth and the requirements. Ask me if anything is genuinely ambiguous; otherwise go ahead and build it.Prefer no fetch? Download scope.md below, drop it in the project, and tell Claude to read it. Anyone with the link can read this spec.
A unified internal bug tracking tool for Ensign's product suite, designed for fast triage, centralised reporting, and multi-product visibility. Built as a standalone Next.js + Postgres app with ensign-sso integration for access control and audit trails. Features Linear-inspired UX, GitHub version context, and client-specific issue tracking.