Automated summary
Conducts a production readiness check by updating implementation status, assessing documentation needs, and verifying alignment with the project vision.
Strengths
- Ensures comprehensive pre-deployment review
- Identifies undocumented features
- Documents strategy alignment
- Generates actionable report
Limitations
- Relies on BROWNFIELD.md and GREENFIELD.md files being maintained
- Does not cover technical debt or performance issues
- Depends on the project's specific structure
Use before deploying any feature or release to verify implementation completeness and strategy coherence.
Do not use when you need automated testing or security auditing; this is a documentation and alignment check only.
Security analysis
SafeThe skill performs only read and edit operations on documentation files and uses glob/grep for scanning. No destructive operations, network calls, or exfiltration.
No concerns found
How this analysis is madeExamples
We are ready to ship the latest version. Run a production readiness check.I've finished implementing the new dashboard. Please do a production check before we deploy.name: production description: Production readiness check from UX perspective - update BROWNFIELD.md with implemented features, check GREENFIELD alignment, note documentation impacts. Use when user says "go to production", "production check", "ready to ship", "pre-release check", or wants to verify implementation status before deployment. allowed-tools: Read, Edit, Glob, Grep, Task
Production Skill
Production readiness check focusing on implementation status and strategy alignment.
When to Use
- Before production deployment
- Feature completion verification
- Strategy alignment check
- Documentation impact assessment
Workflow
Step 1: Update BROWNFIELD.md
Scan codebase and update _OFFICE/BROWNFIELD.md:
-
Identify implemented features:
- Check routes and pages
- Find feature directories
- Look for user-facing components
-
Compare against last production snapshot
-
Document changes:
- Added: New features since last production
- Removed: Features that were removed
- Modified: Significant changes
-
Update Production History table
Step 2: Check Documentation Impacts
Scan changes against documentation:
USER_GUIDE.md:
- List features needing documentation updates
- Identify new features without docs
ONBOARDING.md:
- Check if onboarding elements need updates
- Identify new flows without guidance
Step 3: Check GREENFIELD Alignment
Compare vision against implementation:
- Read
_OFFICE/GREENFIELD.md(vision) - Read
_OFFICE/BROWNFIELD.md(reality) - Assess alignment: High / Medium / Low
- Ask user about any perceived misalignment
- Document strategy changes if needed
Step 4: Generate Readiness Report
## Production Readiness: Implementation Check
### BROWNFIELD Status
- Last Updated: YYYY-MM-DD
- New Features: X added
- Removed Features: X removed
- Modified Features: X changed
### Documentation Impact
- USER_GUIDE.md needs updates: [list or "None"]
- ONBOARDING.md needs updates: [list or "None"]
### Strategy Alignment
- GREENFIELD vision: [summary]
- BROWNFIELD reality: [summary]
- Alignment: High/Medium/Low
### Recommendation
[Ready for production / Needs attention: ...]
Step 5: Confirm with User
Ask: "Production check complete. Ready to proceed with deployment?" Wait for explicit confirmation.
Important
This skill checks implementation status. Use /push for code quality gates and pushing to remote.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/production-readiness-check-mm78nnl4/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/production-readiness-check-mm78nnl4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/production-readiness-check-mm78nnl4/download' --output '.skill-downloads/production-readiness-check-mm78nnl4/SKILL.md.part' && mv '.skill-downloads/production-readiness-check-mm78nnl4/SKILL.md.part' '.skill-downloads/production-readiness-check-mm78nnl4/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Edit, Glob, Grep, Task
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/production-readiness-check-mm78nnl4/SKILL.md' && test -s '.skill-downloads/production-readiness-check-mm78nnl4/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/production' && cp -R '.skill-downloads/production-readiness-check-mm78nnl4' '.claude/skills/production'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/production-readiness-check-mm78nnl4'openskills read 'production-readiness-check-mm78nnl4'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/production-readiness-check-mm78nnl4/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.