How do I install the Production skill?

Run npx skillmds@latest add majiayu000/production-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Production safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Production?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Production free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Production?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Production by majiayu000 — Agent Skill

Name: Production
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Production

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.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

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.

---name: production-2description: 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.--- # 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`: 1. Identify implemented features: - Check routes and pages - Find feature directories - Look for user-facing components 2. Compare against last production snapshot 3. Document changes: - **Added:** New features since last production - **Removed:** Features that were removed - **Modified:** Significant changes 4. 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: 1. Read `_OFFICE/GREENFIELD.md` (vision) 2. Read `_OFFICE/BROWNFIELD.md` (reality) 3. Assess alignment: High / Medium / Low 4. Ask user about any perceived misalignment 5. 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.

Frequently asked questions