Run any Skill in Manus with one click

spec

Stars15

Forks4

UpdatedJuly 2, 2026 at 21:55

Use when a feature request is loose or ambiguous and needs a reviewable spec before planning — turns "add X somehow" into user stories, acceptance criteria, out-of-scope, and open questions via spec_writer

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

byPawel

byPawel/tachibot-mcp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	spec
description	Use when a feature request is loose or ambiguous and needs a reviewable spec before planning — turns "add X somehow" into user stories, acceptance criteria, out-of-scope, and open questions via spec_writer
user-invocable	true

/spec — Request → Reviewable Spec

Collect the request verbatim (do not pre-polish it — ambiguity is input, spec_writer preserves it as open questions).
Gather context: what exists today (read the relevant code if pointed at it), constraints, user base. Pass file paths via files.
Call spec_writer with request, context, files, and format if the user prefers user_story or gherkin (default both).
Relay the spec. Lead with the OPEN QUESTIONS — those are the decisions the user must make; the rest is for review.
Once the user answers/edits, offer the next step: feed the approved spec to planner_maker (or /blueprint) to plan the HOW.

Requires OPENAI_API_KEY. If the tool returns its missing-key error, relay it and suggest /setup.

More from this repository

same repository

audit

byPawel/tachibot-mcp

Use when the user wants a security review of code or a diff — OWASP/CWE findings with severity, taint/data-flow analysis, and concrete fixes via security_review

2026-07-0515

test

byPawel/tachibot-mcp

Use when the user wants tests generated for code or a diff — enumerates edge cases and failure modes first, then emits runnable test code via testgen

2026-07-0515

prompt

byPawel/tachibot-mcp

Use when a task would benefit from a structured thinking technique but you're not sure which — recommends the right prompt technique for the intent (debug, spec, refactor, decision, design) and applies it

2026-07-0315

judge

byPawel/tachibot-mcp

Use for decisions or judgments worth multiple independent perspectives — multi-model council with parallel analysis, search grounding, and synthesis (30-60s); for a quick single-call verdict use the jury tool directly

2026-07-0215

redteam

byPawel/tachibot-mcp

Use when the user shares or finishes a plan and wants it stress-tested before execution — adversarial multi-model pre-mortem with ranked risks, mitigations, and concrete plan edits

2026-07-0215

review

byPawel/tachibot-mcp

Use when code changes are ready for review — a diff exists, the user says "review my changes/PR", or a commit is about to happen. Multi-model diff review (Kimi, DeepSeek, GPT-5.5 panel + Gemini judge) with a MERGEABLE verdict

2026-07-0215

name	spec
description	Use when a feature request is loose or ambiguous and needs a reviewable spec before planning — turns "add X somehow" into user stories, acceptance criteria, out-of-scope, and open questions via spec_writer
user-invocable	true

/spec — Request → Reviewable Spec

Collect the request verbatim (do not pre-polish it — ambiguity is input, spec_writer preserves it as open questions).
Gather context: what exists today (read the relevant code if pointed at it), constraints, user base. Pass file paths via files.
Call spec_writer with request, context, files, and format if the user prefers user_story or gherkin (default both).
Relay the spec. Lead with the OPEN QUESTIONS — those are the decisions the user must make; the rest is for review.
Once the user answers/edits, offer the next step: feed the approved spec to planner_maker (or /blueprint) to plan the HOW.

Requires OPENAI_API_KEY. If the tool returns its missing-key error, relay it and suggest /setup.