finesse-brief skill
finesse-brief turns a line like I want a CRM into a workbench spec: modules, first screen, data model and opening line.
- 128 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill creates a spec file in the project and runs no commands or external service calls.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/finesse-briefDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill creates a spec file in the project and runs no commands or external service calls.
This is third-party code. Review the repository files before installing.
What it does
An architect skill that works before any interface exists and never writes one. It decides what the product is and records the result in `.workbench/spec.md` with YAML frontmatter a builder reads mechanically: purpose, roles, the main subject, the daily first-screen line with its bound fields and who writes them, module page trees and entities. It covers two domains: personal workbenches (gym, pet care, expenses) and system consoles (CRM, ERP, dashboards, project boards). One word like a pet gets a full proposal immediately, while for a CRM the agent asks two questions. Commands include `sketch`, `define`, `hook`, `modules`, `data`, `pages`, `audit`, `monetize` and `handoff`.
Who it is for. Product managers and founders with a vague idea of an internal tool or personal service who need a spec a page can be built from.
Good fit when
- A CRM for a small team must be described before a designer opens Figma.
- An idea for a daily-habit web page will not settle into modules.
- A draft workbench is checked for empty tables on day one.
- The spec must be handed to Cursor, v0 or another interface generator.
Not a fit when
- You need ready layout or interface code: the skill writes neither.
- The project is already designed and only needs implementation.
- A native app is planned: the skill defines web pages, not apps with push.
Example request
/workbench I want a CRM for a five-technician nail studio: ask two questions and deliver a full spec with pages and data.Limitations
The result is always a web page: H5 on a phone or a console in a browser, with no push or background jobs. Documentation and spec text are in Chinese, with a separate English README. The skill builds no interface and is designed to pair with finesse-ui or another page generator. Spec quality depends on your answers to the two questions. Version 0.5.0, so the file format may still change. The last commit dates from August 2026.
How to disable. Delete the skill folder from the agent's skills directory. The generated `.workbench/spec.md` stays in the project as an ordinary document.
FAQ
What is the output?
A `.workbench/spec.md` file. Where there is no filesystem, the skill prints the whole spec in one copyable block.
Does the skill write an interface?
No. It only defines the product and hands the spec to finesse-ui, Cursor, v0 or a person.
How do personal and system modes differ?
Personal: one word gets a full workbench at once. System (CRM, ERP, dashboards): first two questions about the main object, users and frequent action.
What is the data floor?
Each first-screen line names the field, who writes it and the text for when no data exists. Without it the page goes empty by Thursday.
Can it install outside Claude Code?
Yes, `npx skills add` asks which tool to install into. A manual path exists for Cursor and other clients.
Discussion
No questions or reviews yet.
Related
SkillsAn interface design skill that anchors an agent to your product, with an optional MCP server adding real screens from a catalogue.
A Codex skill: three distinct visual concepts, screenshot review and cutting excess, so interfaces look less templated.
A skill with /vspec commands that turns a short requirement into a structured spec, prototype, tests and code.
Skills for spec-driven development: brainstorming, planning, debate-style review and idea grilling before the first commit.
A skill that turns tender documents into a Word technical bid: scoring-based, with industry guides and a 14-step pipeline
A skill for interfaces without the generic AI look: typography, color, motion, component states and a critique of the result.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| finesse-brief (this card) | no | 128 | |
| finesse-skill | no | 976 | builds interfaces from a ready idea; finesse-brief comes before it and defines the product, modules and data |
| prd-taskmaster | no | 610 | turns a goal into a PRD and task graph; here a web workbench spec with first screen and data model |
README in short
The README lists call scenarios, a command table, eleven workbench structures and nine method files in `references/`. Install sections describe the depth of support in each tool.