spec

Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs, including PRD, design docs, roadmap, implementation plan, glossary, key decisions, and index updates. Use for non-trivial design, phasing, PRD, roadmap, or implementation-plan requests.

Jump to install Review files

Repository: tyrchen/tfparser
Last source activity: May 20, 2026 at 00:52
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/tyrchen/tfparser/tree/master/.codex/skills/spec.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/tyrchen/tfparser --skill spec

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name: spec
description: Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs, including PRD, design docs, roadmap, implementation plan, glossary, key decisions, and index updates. Use for non-trivial design, phasing, PRD, roadmap, or implementation-plan requests.

# Spec Use this Codex skill when the user asks for design/specification work before implementation. The canonical workflow is the Claude spec skill at `.claude/skills/spec/SKILL.md`; follow it, with the Codex-specific adjustments below. ## Codex Adjustments - Read `AGENTS.md`, `CLAUDE.md`, `specs/index.md`, and relevant `docs/research/` memos before writing specs. - Use local shell/file tools (`rg`, `sed`, `find`, `cargo` as needed) rather than Claude-only tool names. - Keep the spec set right-sized. Do not create every canonical file unless the system complexity earns it. - If the design depends on unvalidated prior art or performance assumptions, run the `research` skill first. ## Output Rules - Specs live under `specs/`. - Update `specs/index.md` for every spec addition, deletion, or rename. - Numbered specs use build-order numbering already present in this repo. - Roadmap (`90-roadmap.md`) is stakeholder-facing. - Implementation plan (`91-impl-plan.md`) is engineer-facing and dependency-ordered. - Key decisions belong in `99-key-decisions.md`. ## Quality Bar Each component design must pin its purpose, public interface, invariants, non-trivial behavior, tests or gates for those invariants, and cross-references to dependent specs or research. Specs must not silently relax `CLAUDE.md`; explicitly document any necessary deviation.

View on GitHub

Back to search Back to installation

impl

Implement one phase of ./specs/91-impl-plan.md end-to-end, matching the specs and project quality bars, then review the diff and fix valid findings before declaring done. Use when the user asks to build a phase, milestone, next phase, or roadmap slice.

2026-05-20

research

Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user asks to research, study prior art, spike an assumption, compare upstream repos, or learn from pasted GitHub URLs before design or implementation.

2026-05-20

View all from this repository

spec

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository