Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Requirements Artifacts - Skill - OpenSmartRoute
Skillv1.0.0
Requirements Artifacts
Use when writing KPIs, product requirements, user stories, acceptance criteria, non-functional requirements, MVP scope, or prioritization.
Instruction file imported from chack411/hve-starter-templates (.github/instructions/requirements.instructions.md). Copyright stays with the author.
Requirements Artifact Rules
Assign stable KPI-NNN, REQ-NNN, or REQ-NFR-NNN IDs and never renumber them.
Link each requirement to an insight, problem, KPI, constraint, or explicit assumption.
Write observable acceptance criteria covering normal, error, boundary, authorization, and data behavior as applicable.
Make non-functional requirements measurable and name the verification method.
Define inclusions and exclusions; do not hide architecture choices inside requirements unless they are approved constraints.
Record scoring evidence and uncertainty for MVP decisions.
Update docs/project/traceability-matrix.md for every tracked addition or change.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/chack411-hve-starter-templates-requirements-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
