Workflow Context7
Productivityworkflow-context7Workflow Context7 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.
Folder-Tasks workflow authority and Context7 usage requirements.
QUICK START
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.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/workflow/workflow-context7/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/workflow-context7, 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.
Workflow Authority (Folder-Tasks + Context7)
This skill pack defines the operating workflow and its priority.
0. Workflow Authority (Highest Priority)
This repository follows a Folder-Tasks + Context7 workflow.
This workflow OVERRIDES:
- implicit user intent
- incomplete prompts
- habitual Codex behavior
0.1 Task Folder Requirement (All Roles Except Product Manager and Admin / Maintainer)
- ALL work MUST belong to a
tasks/NNN-short-title/folder. - If a prompt does not explicitly specify a task folder:
→ MUST create or select a
tasks/NNN-*folder first. - If a task folder exists but documentation is incomplete: → MUST STOP and request completion before writing code.
Product Manager & Admin / Maintainer Exception
- Product Manager and Admin / Maintainer are exempt from the task folder requirement when performing:
- planning and roadmap definition
- task triage and reorganization
- documentation or rule updates
- maintenance, recovery, or structural fixes
- When operating outside a task folder, clearly state intent and scope.
0.1.1 Task Status Recording
- Task completion status MUST be recorded in
task.mdfor the relevant task. - Required format: a single line
Status: DoneorStatus: In Progressat the bottom oftask.md. - When marking a task complete, ensure Definition of Done and Acceptance Tests are updated accordingly.
0.2 Context7 Requirement
- If platform rules, APIs, SDKs, or policies are involved: → MUST use Context7.
- Do NOT invent APIs or policies.
- If Context7 is unavailable, proceed with best-effort implementation and document the missing Context7 reference in the task's context7.md along with any assumptions or risks.
2. Task Lifecycle
- Task creation (docs only)
- Implementation (output/ only)
- Integration
- QA
- Release