When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
A toolkit for the full lifecycle of software requirements specifications, from analysing requirements and writing user stories to defining designs, rules, permissions, interfaces, acceptance checks, changes, and reviews.
Derive acceptance criteria and verification points from requirements, user stories, functional design, or spec sections. Use when Codex needs to define how a feature, flow, or document section will be checked, reviewed, or accepted.
Extract, organize, and write business rules from requirements, meeting notes, functional design, or draft specs. Use when Codex needs to turn scattered logic into clear rule statements, decision conditions, calculation rules, state constraints, or exception rules.
Turn analyzed requirements into a functional design note covering function decomposition, business rules, state changes, exception handling, roles, permissions, and interface or data constraints. Use when Codex needs to bridge requirement analysis and formal spec writing with a reviewable functional solution.
Generate, rewrite, or standardize a full Chinese requirements specification document aligned to the GJB 438C style from chapter 1 through chapter 7, while strictly preserving the user's Word template structure and fixed terminology.
Organize interface contracts, field definitions, validation rules, enums, ranges, units, and data mappings from requirement drafts, design notes, or specifications. Use when Codex needs to make data constraints explicit for specs, integration design, review, or development handoff.
A workflow tool for changing requirements or features in an existing codebase, especially Chrome extensions. It covers confirming acceptance criteria and current behaviour, assessing impact, designing changes, implementing small diffs, and running regression checks.
Generate, rewrite, or standardize Chapter 3 of a Chinese requirements specification document, especially section 3.2 CSCI capability requirements, under a confirmed template structure.
Review a Chinese requirements specification generated from a Word template, focusing on template compliance, function-description quality, table-head preservation, chapter completeness, traceability, and delivery readiness.
Generate, rewrite, or standardize the remaining sections of a Chinese requirements specification document from section 3.3 through chapter 7, under a confirmed template structure.
Define roles, permissions, responsibilities, and access boundaries from requirements, process descriptions, or system drafts. Use when Codex needs to clarify who can do what, under which conditions, and with which data scope.
Coordinate Chinese specification-writing work across the spec-writing skill suite. Use when the user says /spec-writing, mentions spec-writing, or wants to write, rewrite, standardize, review, split, or complete a Chinese requirements or specification document from inputs such as Word templates, existing .docx specs…
Write state transitions, node conditions, exception branches, rollback logic, and recovery rules from requirements, process drafts, or functional design. Use when Codex needs to make state machines and abnormal flows explicit before detailed design, test design, or formal specs.
Convert analyzed requirements, business flows, or feature ideas into structured Chinese user stories with clear actors, scenarios, goals, and acceptance cues. Use when Codex needs to express requirements from the user perspective before or during functional design and spec writing.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking,"…
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Lifecycle manager for GitHub-based skills. Use this to batch scan your skills directory, check for updates on GitHub, and perform guided upgrades of your skill wrappers.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
★not rated 2 1mo agoA21 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: