Run any Skill in Manus with one click

create-techspec

Stars0

Forks1

UpdatedMay 21, 2026 at 01:47

Create implementation-ready Technical Specifications from complete PRDs. Use when Codex is asked to create, draft, generate, or save a tech spec; translate a PRD into architecture and implementation guidance; define interfaces, models, endpoints, integration points, testing strategy, observability, sequencing, or technical risks; or create files under tasks/prd-[feature-name]/techspec.md.

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

rodrigobranas

rodrigobranas/aidev_axon_7

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

File Explorer

4 files

SKILL.md

readonly

name	create-techspec
description	Create implementation-ready Technical Specifications from complete PRDs. Use when Codex is asked to create, draft, generate, or save a tech spec; translate a PRD into architecture and implementation guidance; define interfaces, models, endpoints, integration points, testing strategy, observability, sequencing, or technical risks; or create files under tasks/prd-[feature-name]/techspec.md.

Create TechSpec

Core Workflow

Use this skill to turn an existing PRD into a concise, implementation-ready technical specification saved in the project task structure.

Read resources/create-techspec.md before starting. Treat that file as the canonical workflow for this skill.

Load resources/techspec-template.md only after PRD analysis, project exploration, research, and technical clarification, when drafting the tech spec. Treat that file as the required TechSpec template standard.

Execution Rules

Confirm and read the PRD at tasks/prd-[feature-name]/prd.md.
Explore the project before asking technical clarifying questions.
Use Context7 MCP for technical documentation questions when relevant.
Use web search for business rules and general information before clarifying when the workflow requires it.
Ask focused technical clarifying questions before drafting the tech spec.
Generate the tech spec from the exact template in resources/techspec-template.md.
Focus on technical guidance and architecture; do not implement code.
Avoid repeating PRD functional requirements except where needed to anchor technical choices.
Save the final tech spec to tasks/prd-[feature-name]/techspec.md.
Report the final file path and confirmation.

Expected Inputs

Typical input is a PRD path, feature name, or request such as:

"Use $create-techspec for tasks/prd-team-invitations/prd.md."
"Create a tech spec for the checkout-flow PRD."
"Turn this PRD into an implementation-ready technical specification."

If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible PRDs exist.

More from this repository

same repository

create-prd

rodrigobranas/aidev_axon_7

Create Product Requirements Documents (PRDs) from feature requests using a required clarify-plan-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a PRD, product requirements document, product spec, feature requirements document, or requirements artifact that should be saved as tasks/prd-[feature-name]/prd.md.

2026-05-210

create-tasks

rodrigobranas/aidev_axon_7

Create implementation task lists and individual task files from an existing PRD and Tech Spec. Use when Codex is asked to write, generate, create, draft, or update feature tasks, implementation tasks, task breakdowns, delivery plans, or task files based on tasks/prd-[feature-name]/prd.md and tasks/prd-[feature-name]/techspec.md.

2026-05-210

create-techspec

rodrigobranas/aidev_axon_7

Create implementation-ready Technical Specifications from existing PRDs using a required analyze-research-clarify-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a Tech Spec, technical specification, implementation specification, architecture spec, or engineering plan based on tasks/prd-[feature-name]/prd.md and save it as tasks/prd-[feature-name]/techspec.md.

2026-05-210

execute-bugfix

rodrigobranas/aidev_axon_7

Fix documented QA bugs for a feature by reading bugs.md, qa.md, PRD, Tech Spec, and tasks; planning fixes by severity; implementing root-cause fixes; adding regression tests; validating with project tests and Playwright for UI bugs; and updating bugfix artifacts. Use when Codex is asked to fix bugs, resolve QA findings, address failed QA, or complete bugfix work in tasks/prd-[feature-name]/.

2026-05-210

execute-qa

rodrigobranas/aidev_axon_7

Execute QA validation for a completed feature against its PRD, Tech Spec, and tasks using Playwright MCP, accessibility checks, visual review, bug documentation, and a final QA report. Use when Codex is asked to test, QA, validate, approve, reject, or verify a feature implementation in tasks/prd-[feature-name]/.

2026-05-210

execute-review

rodrigobranas/aidev_axon_7

Execute a code review for implemented work by analyzing git diff, reading modified files, checking project rules and skills, verifying Tech Spec and task adherence, running tests, identifying code quality issues, and saving a code review report. Use when Codex is asked to review code, validate implementation quality, approve changes, or produce codereview.md for a feature or project change.

2026-05-210

name	create-techspec
description	Create implementation-ready Technical Specifications from complete PRDs. Use when Codex is asked to create, draft, generate, or save a tech spec; translate a PRD into architecture and implementation guidance; define interfaces, models, endpoints, integration points, testing strategy, observability, sequencing, or technical risks; or create files under tasks/prd-[feature-name]/techspec.md.

Create TechSpec

Core Workflow

Use this skill to turn an existing PRD into a concise, implementation-ready technical specification saved in the project task structure.

Read resources/create-techspec.md before starting. Treat that file as the canonical workflow for this skill.

Execution Rules

Confirm and read the PRD at tasks/prd-[feature-name]/prd.md.
Explore the project before asking technical clarifying questions.
Use Context7 MCP for technical documentation questions when relevant.
Use web search for business rules and general information before clarifying when the workflow requires it.
Ask focused technical clarifying questions before drafting the tech spec.
Generate the tech spec from the exact template in resources/techspec-template.md.
Focus on technical guidance and architecture; do not implement code.
Avoid repeating PRD functional requirements except where needed to anchor technical choices.
Save the final tech spec to tasks/prd-[feature-name]/techspec.md.
Report the final file path and confirmation.

Expected Inputs

Typical input is a PRD path, feature name, or request such as:

"Use $create-techspec for tasks/prd-team-invitations/prd.md."
"Create a tech spec for the checkout-flow PRD."
"Turn this PRD into an implementation-ready technical specification."

If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible PRDs exist.