/fstack
The front door for fstack. Read what the user wants. Pick one skill. Run it. Stop.
When to use
- The user invokes
/fstack.
- The user asks which fstack skill fits their task.
- The user describes work and mentions fstack without naming a skill.
Steps
- Read the user's request.
- If there is no task — the user typed
/fstack alone, or just asked what fstack can do — list the twelve skills with a one-line description each, then stop and ask what they want to do. Do not route or guess. This is the menu below.
- If there is a task — match it to one of the twelve skills below.
- Say which skill you picked and why, in one sentence.
- Run that skill. Do not chain others.
The skills
When there is no task, show this list:
| Skill |
What it does |
/fstack-roast |
Stress-test a product idea. Ends with a verdict and the smallest version worth building. |
/fstack-interview |
Ask about the product — demand, customer, pricing, risks — and record the answers in AGENTS.md. |
/fstack-nail |
Clarify a vague task, nail down a 3-line summary, and get your yes before planning. |
/fstack-plan |
Write a one-page plan with a mandatory "what we're NOT doing" section. |
/fstack-build |
Implement the plan one small step at a time, asking at real choices. |
/fstack-simplify |
Audit for unnecessary complexity and propose deletions — one file or the whole codebase. |
/fstack-design |
Make UI match the project's existing styles and clean up design slop. |
/fstack-counselors |
Ask the 3 most capable models the same question and synthesize one verdict. |
/fstack-check |
Review finished work: does it work, does it match the plan, is it simple. |
/fstack-document |
Write docs/ for the project, ELI5 to deep. Run again to update them. |
/fstack-learn |
Capture one lesson in three lines, so future sessions start smarter. |
/fstack-push |
Commit the current task's changes and push to the remote. Nothing else. |
Routing map
| Situation |
Skill |
| Product idea, not sure it's worth building |
/fstack-roast |
| New project, the agent lacks business context |
/fstack-interview |
| Vague or unclear task |
/fstack-nail |
| Idea is clear, no plan exists |
/fstack-plan |
| Plan exists and is approved |
/fstack-build |
| Feels bloated or sloppy — one file or the whole codebase |
/fstack-simplify |
| UI looks off or inconsistent with the rest |
/fstack-design |
| Big decision, one opinion is not enough |
/fstack-counselors |
| Work is done, needs review |
/fstack-check |
| Project needs docs, or the docs have gone stale |
/fstack-document |
| Something worth remembering just happened |
/fstack-learn |
| Just want it committed and pushed |
/fstack-push |
Stop and ask
If you truly cannot tell which skill fits, ask one clarifying question. Then route.
If still ambiguous after the answer, route to /fstack-nail. That is what it is for.
Must NOT
- Route when there is no task. List the skills and ask instead.
- Chain multiple skills. Pick one, run it, stop.
- Ask more than one clarifying question before routing.
- Plan, code, or review inside this skill. Route and hand off.
Example
User: /fstack
Agent: (lists the twelve skills with one-line descriptions) "That's the full set. What do you want to do?"
User: /fstack I want to add dark mode to my site
Agent: "This leaves important choices open, so I'll start with /fstack-nail to make sure I understand what you want." (runs /fstack-nail)
1---2name: fstack3description: The fstack front door. Invoke /fstack alone to list every skill, or with a task to route it to the right one.4---56# /fstack78The front door for fstack. Read what the user wants. Pick one skill. Run it. Stop.910## When to use1112- The user invokes `/fstack`.13- The user asks which fstack skill fits their task.14- The user describes work and mentions fstack without naming a skill.1516## Steps17181. Read the user's request.192. **If there is no task** — the user typed `/fstack` alone, or just asked what fstack can do — list the twelve skills with a one-line description each, then stop and ask what they want to do. Do not route or guess. This is the menu below.203. **If there is a task** — match it to one of the twelve skills below.214. Say which skill you picked and why, in one sentence.225. Run that skill. Do not chain others.2324## The skills2526When there is no task, show this list:2728| Skill | What it does |29|---|---|30| `/fstack-roast` | Stress-test a product idea. Ends with a verdict and the smallest version worth building. |31| `/fstack-interview` | Ask about the product — demand, customer, pricing, risks — and record the answers in AGENTS.md. |32| `/fstack-nail` | Clarify a vague task, nail down a 3-line summary, and get your yes before planning. |33| `/fstack-plan` | Write a one-page plan with a mandatory "what we're NOT doing" section. |34| `/fstack-build` | Implement the plan one small step at a time, asking at real choices. |35| `/fstack-simplify` | Audit for unnecessary complexity and propose deletions — one file or the whole codebase. |36| `/fstack-design` | Make UI match the project's existing styles and clean up design slop. |37| `/fstack-counselors` | Ask the 3 most capable models the same question and synthesize one verdict. |38| `/fstack-check` | Review finished work: does it work, does it match the plan, is it simple. |39| `/fstack-document` | Write docs/ for the project, ELI5 to deep. Run again to update them. |40| `/fstack-learn` | Capture one lesson in three lines, so future sessions start smarter. |41| `/fstack-push` | Commit the current task's changes and push to the remote. Nothing else. |4243## Routing map4445| Situation | Skill |46|---|---|47| Product idea, not sure it's worth building | `/fstack-roast` |48| New project, the agent lacks business context | `/fstack-interview` |49| Vague or unclear task | `/fstack-nail` |50| Idea is clear, no plan exists | `/fstack-plan` |51| Plan exists and is approved | `/fstack-build` |52| Feels bloated or sloppy — one file or the whole codebase | `/fstack-simplify` |53| UI looks off or inconsistent with the rest | `/fstack-design` |54| Big decision, one opinion is not enough | `/fstack-counselors` |55| Work is done, needs review | `/fstack-check` |56| Project needs docs, or the docs have gone stale | `/fstack-document` |57| Something worth remembering just happened | `/fstack-learn` |58| Just want it committed and pushed | `/fstack-push` |5960## Stop and ask6162If you truly cannot tell which skill fits, ask **one** clarifying question. Then route.6364If still ambiguous after the answer, route to `/fstack-nail`. That is what it is for.6566## Must NOT6768- Route when there is no task. List the skills and ask instead.69- Chain multiple skills. Pick one, run it, stop.70- Ask more than one clarifying question before routing.71- Plan, code, or review inside this skill. Route and hand off.7273## Example7475> User: `/fstack`76>77> Agent: *(lists the twelve skills with one-line descriptions)* "That's the full set. What do you want to do?"7879> User: `/fstack I want to add dark mode to my site`80>81> Agent: "This leaves important choices open, so I'll start with `/fstack-nail` to make sure I understand what you want." *(runs /fstack-nail)*
flaviocopes