Define contract-level behavior specifications before execution planning.
npx skills add https://github.com/xiongxianfei/rigorloop --skill spec-xiongxianfei
Please help me install this Agent Skill. Skill: spec Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/spec Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill spec-xiongxianfei
Writing contract-level specifications before execution planning ensures that system behavior, APIs, UI, data contracts, error handling, and security requirements are clearly defined and verifiable.
Create a new spec document under specs/slug.md to begin detailing the contract before planning.
High-intent search queries and answers about installing and using this skill.
To write a contract-level specification, define externally observable behavior, APIs, UI, data contracts, and error handling. Include status, goals, inputs/outputs, constraints, acceptance criteria, and risks to ensure clear, testable expectations before execution planning.
A specification artifact for API and UI changes should include status, goals, inputs/outputs, constraints, acceptance criteria, risks, and follow-on artifacts. This ensures clear, testable expectations for externally observable behavior and data formats.
You need a contract-level spec when making changes affecting externally observable behavior, APIs, UI, config, data contracts, error handling, compatibility, security, or safety-sensitive logic across software systems to reduce ambiguity and rework.
To start drafting a new feature specification, create a document to capture goals, success criteria, and acceptance tests. This guides design and implementation by establishing observable contracts before changes are made.
The best way to define testable expectations for system behavior is to draft a contract-level specification that captures inputs, outputs, constraints, and acceptance criteria, serving as a canonical reference for APIs and data formats.
Writing specifications before planning reduces rework by establishing observable contracts early. This defines clear, verifiable expectations for system behavior, APIs, and UI flows across teams.
cshyangPlan and execute a project discovery phase to define requirements and scope.
EricOo0Generate implementation plans specifying files, tests, docs, and commit steps.
Lev-itIdentifies and categorizes product launch risks from PRDs or plans.
dralgorhythmGenerate Product Requirements Documents with user stories and Given/When/Then acceptance criteria.
