auto-frame

Transform user requests into bounded SPEC.md project specifications.

37|7|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/appautomaton/mlx-speech --skill auto-frame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-frame
Source: https://github.com/appautomaton/mlx-speech/tree/main/.claude/skills/auto-frame
Command: npx skills add https://github.com/appautomaton/mlx-speech --skill auto-frame

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes references (resource) components.

What problem does it solve?

This Skill solves the problem of ambiguous project requests by forcing a structured, bounded definition of work before any implementation begins, preventing scope creep and misalignment.

Core Features & Use Cases

  • Bounded Specification: Generates a canonical SPEC.md that serves as a reloadable contract for the project.
  • Diagnostic Framing: Uses mode-specific diagnostics (Startup, Builder, Content) to clarify intent, stakeholders, and success criteria.
  • Use Case: When starting a new feature or refactor, use this Skill to transform a vague "make it faster" request into a concrete, testable plan with defined anti-goals and acceptance criteria.

Quick Start

Use the auto-frame skill to initiate a new project specification based on the current user request.

Frequently Asked Questions about auto-frame

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague product request into a bounded specification?

To turn a vague product request into a bounded specification, apply structured diagnostic framing to clarify stakeholder intent, define anti-goals, and generate a canonical SPEC.md artifact with testable acceptance criteria.

What is the best way to define project scope and prevent scope creep?

The best way to define project scope and prevent scope creep is by standardizing requirement decomposition into a bounded SPEC.md contract before implementation, ensuring architectural and product consistency across workflows.

Does auto-frame support specification for startup, builder, and content workflows?

Yes, auto-frame supports specification for startup, builder, and content workflows by using mode-specific diagnostics to clarify intent, stakeholders, and success criteria tailored to each context.

How do I create a SPEC.md artifact that aligns with repository-level steering?

You create a SPEC.md artifact aligned with repository-level steering by transforming project requests into bounded specifications that integrate with existing roadmap documentation to ensure architectural consistency.

Do I need Node.js to generate project specifications with auto-frame?

Yes, you need Node.js installed as a dependency to run auto-frame and generate standardized project specification artifacts from user requests.

Why should I use diagnostic framing before starting a feature refactor?

You should use diagnostic framing before a feature refactor to force a structured, bounded definition of work, transforming ambiguous requests into concrete plans and preventing stakeholder misalignment.