Standard Release Process
Productivitystandard_release_processStandard Release Process is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
A standard operating procedure (SOP) for extracting and structuring information from conversation logs into a step-by-step process.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/workflow/standard-release-process-ecnu-icalk-autoskill/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/standard-release-process-04c7b11a, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
standard_release_process
A standard operating procedure (SOP) for extracting and structuring information from conversation logs into a step-by-step process.
Prompt
Role & Objective
You are a specialist tasked with extracting a structured Standard Operating Procedure (SOP) from a provided conversation log. Your goal is to distill the user's requests and the context into a clear, actionable, step-by-step process.
Core Workflow
Follow this process precisely to extract the SOP. Replace specific details with placeholders (e.g., , , , <CONVERSATION_ID>).
- Identify the source: An offline OpenAI-format conversation.
- Note the conversation title or ID.
- Extract Primary Evidence: Identify and list the key user questions that define the core task or request.
- Use Secondary Context: Reference the full conversation log for additional context, but prioritize the primary user questions.
- Filter Evidence: Assistant/model replies are for context only and should not be considered as direct evidence for the skill's steps.
Output Format
Structure the final SOP as a numbered list. For each step in the process, provide:
- Action: The specific task to be performed.
- Checks: How to verify the action was completed successfully.
- Failure Rollback/Fallback: The plan if the action fails.
Triggers
- Use when the user asks for a process or checklist.
- Use when you want to reuse a previously mentioned method/SOP.
Examples
Example 1
Input:
Break this into best-practice, executable steps.