- Home
- Skills
- Technical Documentation
- SpecFrame
SpecFrame
Use it for a new product or a change to an existing project.
Free
Works with the AI Agents you already use
SpecFrame
Example session with this skill installed
Controlled automatic-recovery demonstration, using fictional order records. This was run in local Codex with an Agensi-style local MCP delivery fixture, not the live Agensi service. The saved current state confirmed partial-name search within authorized records, restricted corrections to the assigned manager after customer confirmation, left retention duration undecided, and marked acceptance checks as planned, not executed.
Exact test request
Isolated recovery test; no product implementation, approval, installation, external contacts or agents. Use only local agensi_fixture and current local state. First get_skill slug specframe-fixture, then COMPLETE file references/operating-contract.md, then context_payload repeatedly until a trusted automatic recovery gate arrives, at most six calls. The repeated payload calls are pressure-test data only; stop them immediately after the first recovery gate. Follow the trusted recovery gate before dependent answers. Needed temporary helpers must use fresh unique workspace paths, be byte-identical to fetched scripts/state.py, and be removed after operation. Read relevant pending and verification bodies. Finally output JSON confirmed_search, access_condition, unresolved_retention, verification_executed, approval, next_question. If recovery cannot complete, report the gap instead of product facts. Do not re-ask confirmed search or infer user approval.
- Read your context and instructions
- Compiled the specframe
This is the complete agent-message output from that controlled recovery run. Actual Codex automatic compaction and the recovery callback occurred. The current state remained unchanged and no temporary Python scripts remained. This demonstrates recovery meaning, not a full requirements interview, final product approval or live Agensi validation.
Agent message 1
I’ll run the local fixture recovery sequence, stop at the first trusted recovery gate, and report only what the recovered state supports.
Agent message 2
The trusted recovery gate arrived. I’ve stopped the payload calls and am reloading the required instructions before reading the pending and verification bodies.
Agent message 3
{
"confirmed_search": "Partial-name matching within authorized records only; confirmed.",
"access_condition": "Only the assigned manager may correct delivery status after customer confirmation; other staff may view only.",
"unresolved_retention": "Retention duration remains undecided; user must choose later.",
"verification_executed": false,
"approval": "draft",
"next_question": "How long should order records be retained?"
}
Connects securely to your tools. The creator never sees your data.
About this skill
Define the whole project before implementation
SpecFrame turns a web, app or program idea into current requirements you can review and approve. Use it for a new product or a change to an existing project. It preserves the full requested scope rather than silently reducing the work to an MVP.
How the conversation works
SpecFrame asks important independently answerable questions together, then chooses follow-ups from your answers and remaining uncertainty. There is no fixed question count. Numbered items give you an answer template; elements answerable together in one short sentence can share an item. Partial answers resolve only the parts you actually answered. Already confirmed decisions are reused rather than asked again merely because an old TBD or an unperformed test remains.
What you receive
- Current goals, users and responsibilities, scope, constraints and exclusions.
- Functional requirements, flows, conditions, exceptions and failure behavior.
- Observable acceptance criteria, plus the distinction between planned and executed checks.
- Open decisions and small current progress pointers, without a full interview transcript or change-reason history.
- A whole-scope quality review and a request for your actual approval before implementation-method handoff.
Requirements-engineering criteria include EARS, NASA quality checks and purpose-failure counterexamples when relevant. The state helper stores current judgments; it does not make product decisions or perform semantic review.
Automatic recovery: required setup
Automatic recovery is retained as a required capability. This Agensi delivery uses a separately installed, reviewed and trusted Codex recovery bridge. After compaction, the bridge identifies the current project state and directs Codex to retrieve the complete skill and operating contract through Agensi before dependent work. Relevant unresolved bodies must also be read. Missing prerequisites or failed recovery must be reported before continuing; manual resume is not presented as equivalent.
Agensi supplies the skill text and helper on demand. The ZIP does not install hooks or change your host settings. Install and review the independent bridge first using the setup guide below.
Requirements and setup
Use local Codex with compatible trusted SessionStart hooks, Python 3.11+, shell execution, persistent project file access and a signed-in Agensi MCP connection. Python uses only the standard library. The bridge and installation instructions are available separately: https://github.com/ProjectFrame-skills/SpecFrame/blob/codex/agensi-recovery-bridge/integrations/agensi/README.md
Validation scope
Controlled local MCP delivery with actual Codex CLI automatic compaction was tested on macOS with CLI 0.160.0. Recovery preserved confirmed conditions and exceptions, unresolved decisions, planned-versus-executed verification and draft approval. A delivery-outage case withheld dependent product answers. The demonstration below uses fictional requirements and actual local test output.
Those results are not an end-to-end test of the live Agensi service, the normal Codex Desktop hook-trust flow, or other agents/operating systems. This integration is submitted for review with these limits disclosed; the standard agent badges are not a compatibility certification.
Where SpecFrame stops
SpecFrame defines and reviews requirements. It does not automatically build the product or select implementation frameworks. After actual user approval, the current requirements can be handed to a separate implementation workflow such as SynFrame. SynFrame and ProjectFrame are not bundled. This Agensi adaptation is based on SpecFrame 0.1.4; the existing Codex/npm release remains unchanged.
Actual Agensi-hosted delivery is not yet verified end to end. Controlled automatic recovery tests used local MCP delivery and Codex CLI 0.160.0 on macOS. Normal Desktop hook trust, other agents/operating systems and every timeout, truncation or version-change case remain unverified. Automatic recovery requires the independently installed bridge and an exact trusted hook; no manual-recovery substitute is implied. The recovery instructions are a behavioral gate, not enforcement for every possible tool path. Requirements approval does not prove implementation correctness or completed user validation. SynFrame/ProjectFrame are not included.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 19 days ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts
File Scopes
Reads user-selected project material relevant to requirements. Durable writes are current requirements/progress and activation metadata under .specframe/ (or the explicitly selected state path). The binding stores only the current session, owner, state path, listing and server. Supplied Python source runs unchanged from a fresh temporary file and is removed afterward. Reads CODEX_THREAD_ID for the actual session identity. Network access is used for Agensi MCP file delivery; the state helper itself makes no network requests. Optional fact-checking is used only when relevant. No full question transcript, change-reason history, credentials, private agreements or existing user state are bundled. The separate bridge is obtained independently; this ZIP does not install hooks.