Run any Skill in Manus with one click

tech-spec-review

Stars4

Forks2

UpdatedApril 20, 2026 at 06:43

Review a technical specification for gaps, confusing explanations, and contradictory specifications. Use when user asks to review, critique, or audit a tech spec, design doc, PRD, or RFC for high-level clarity and consistency. Does not suggest implementation details.

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

lttr

lttr/dotfiles

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	tech-spec-review
description	Review a technical specification for gaps, confusing explanations, and contradictory specifications. Use when user asks to review, critique, or audit a tech spec, design doc, PRD, or RFC for high-level clarity and consistency. Does not suggest implementation details.
disable-model-invocation	true

Tech Spec Review

Review this design doc.

Identify gaps in the design, confusing explanations, or contradictory specifications. Avoid suggestions about implementation details, and focus on high-level design and clarity.

Cite specific quotes and section headings. Do not rely on line numbers, as they're likely to change during editing.

More from this repository

same repository

implement

lttr/dotfiles

Implement work from a ticket, spec, or inline description; auto-detects the next item from the task folders when no argument is given.

2026-07-214

next-steps

lttr/dotfiles

Show status overview and next steps for an .aiwork/ spec. Use when user says "next steps", "what's left", "status", "progress", or wants to see what's planned, unplanned, or incomplete for a task.

2026-07-214

skills-map

lttr/dotfiles

Scan current directory (recursively) for Claude Code skills, slash commands, agents, hooks, and plugin/MCP configs, then render an interactive HTML graph of their explicit and implicit relationships. Use when the user says "skills map", "skill graph", "visualize skills", "map skills", "how do my skills relate", or wants to audit a skill collection before publishing.

2026-07-214

to-spec

lttr/dotfiles

Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.

2026-07-214

to-tickets

lttr/dotfiles

Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.

2026-07-214

aiwork-protocol

lttr/dotfiles

Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (triage, research, spec, prd, plan, review, notes, docs/). Use when the user asks to plan, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.

2026-07-214

Run any Skill with one click