Run any Skill in Manus with one click

to-spec

Stars3

Forks0

UpdatedJuly 14, 2026 at 13:35

Turn the current conversation into a spec and save it under .scratch/specs/ — no interview, just synthesis of what you've already discussed. Use only when the user explicitly invokes `to-spec` or `$to-spec`; do not auto-invoke from context.

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

flexdinesh

flexdinesh/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	to-spec
description	Turn the current conversation into a spec and save it under .scratch/specs/ — no interview, just synthesis of what you've already discussed. Use only when the user explicitly invokes `to-spec` or `$to-spec`; do not auto-invoke from context.
disable-model-invocation	true

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.

Save the completed spec under .scratch/specs/<feature-slug>.md, creating the directory if needed. There is no external issue tracker or triage setup.

Process

Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

Write the spec using SPEC.md and save it under .scratch/specs/<feature-slug>.md.

More from this repository

same repository

grill

flexdinesh/agent-skills

A relentless interview to sharpen a plan or design, maintain the domain language, and chart large efforts until their route is clear. Use only when the user explicitly invokes `grill` or `$grill`; do not auto-invoke from context.

2026-07-143

implement

flexdinesh/agent-skills

Implement a piece of work based on a spec or set of tickets. Use only when the user explicitly invokes `implement` or `$implement`; do not auto-invoke from context.

2026-07-143

to-tickets

flexdinesh/agent-skills

Break a plan, spec, or the current conversation into tracer-bullet tickets under .scratch/, each declaring its blocking edges. Use only when the user explicitly invokes `to-tickets` or `$to-tickets`; do not auto-invoke from context.

2026-07-143

adr

flexdinesh/agent-skills

Save a brief Architecture Decision Record (ADR) from the current session. Use only when the user explicitly invokes `adr` or `$adr`; do not auto-invoke from context.

2026-07-133

pi-extension

flexdinesh/agent-skills

Build extensions for Pi. Use only when the user explicitly invokes `pi-extension` or `$pi-extension`; do not auto-invoke from context.

2026-06-203

opencode-plugin

flexdinesh/agent-skills

Build plugins for OpenCode. Use only when the user explicitly invokes `opencode-plugin` or `$opencode-plugin`; do not auto-invoke from context.

2026-06-203

name	to-spec
description	Turn the current conversation into a spec and save it under .scratch/specs/ — no interview, just synthesis of what you've already discussed. Use only when the user explicitly invokes `to-spec` or `$to-spec`; do not auto-invoke from context.
disable-model-invocation	true

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.

Save the completed spec under .scratch/specs/<feature-slug>.md, creating the directory if needed. There is no external issue tracker or triage setup.

Process

Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

Write the spec using SPEC.md and save it under .scratch/specs/<feature-slug>.md.