workflow
Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.
Best use case
workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.
Teams using workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How workflow Compares
| Feature / Agent | workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Project Workflow Skill Use this skill for any non trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Activate with: `@update` (for docs sync only) ## Triage first Before changing code: 1. Identify what is missing, broken, or incomplete. 2. Theorize a few likely causes or approaches. 3. Narrow to the most likely plan. 4. Ask if anything important is still unclear. Skip the long process only for obvious one file fixes like typos or tiny copy changes. ## PRD rules Create a PRD before non trivial work. - Path: `prds/<feature-or-problem-slug>.md` - Extension: `.md` - Include: - problem - root cause for bugs - proposed solution - files to change - edge cases - verification steps - task completion log Add metadata at the top: - `Created: YYYY-MM-DD HH:mm UTC` - `Last Updated: YYYY-MM-DD HH:mm UTC` - `Status: Draft | In Progress | Done` ## Task tracking Update `task.md` as the work moves forward. - Put new work under `## to do` - Move finished work to `## completed` - Add timestamps in `YYYY-MM-DD HH:mm UTC` - Do not mark a task done until it has been verified - Keep task notes short but specific enough for the next session When useful, include: - the PRD path - the files touched - the verification command or outcome ## Docs sync after changes After each feature or fix, sync the project docs: - `task.md` - `changelog.md` - `files.md` For `changelog.md`: - use Keep a Changelog structure - get real dates from `git log --date=short -n 10` - add timestamps when helpful For `files.md`: - add new files - update descriptions that changed - keep descriptions brief and concrete ## Execution style - Use subagents for research or parallel analysis when the task is large enough to benefit. - Use one focused subagent per task. - Stop and re plan if the work stops making sense. - Keep the change set tight. - Ask whether a staff engineer would approve the result before calling it done. ## Learning loop If the user corrects a repeated pattern, record the lesson in `prds/lessons.md` so the mistake does not come back.
Related Skills
Update project docs
Use this skill after completing any feature, fix, or migration to keep the three core project tracking files in sync.
robel-auth
Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.
Create a PRD
Use this skill before any multi-file feature, architectural decision, or complex bug fix.
convex-self-hosting
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other frontends.
convex-return-validators
Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.
convex-doctor
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.
write
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.
sec-check
Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code. Use when reviewing code that touches user data, PII, or access control.
schema-builder
Design and generate Convex database schemas with proper validation, indexes, and relationships. Use when creating schema.ts or modifying table definitions.
real-time-backend
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
react-effect-decision
Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.
migration-helper
Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations. Use when schema changes affect existing data.