원클릭으로
culture-document
Writes company culture documents with values, behaviors, rituals, and how culture shows up in daily work for team alignment.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Writes company culture documents with values, behaviors, rituals, and how culture shows up in daily work for team alignment.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
A demo skill for tests.
Writes website accessibility policies with WCAG compliance commitments and accommodation procedures. Use when creating an accessibility statement for your website.
Creates a complete client onboarding system for agencies and service providers, including welcome email sequence, intake questionnaire, kickoff meeting checklist, and communication guidelines. Use when a user runs an agency, consultancy, or service business and needs to standardize how new clients are brought on board.
Facilitates annual business planning with vision setting, goal cascading, quarterly milestones, and resource allocation for focused execution.
Compiles annual business reviews with year-over-year metrics, milestone highlights, lessons learned, and strategic goals for the upcoming year. Use when a user needs to reflect on their business year, wants to create a year-in-review document for stakeholders, or is setting annual goals and needs to assess where they stand.
Creates API documentation templates with endpoint descriptions, request/response examples, and authentication guides. Use when documenting REST APIs for developers.
| name | culture-document |
| description | Writes company culture documents with values, behaviors, rituals, and how culture shows up in daily work for team alignment. |
| allowed-tools | Read Write Glob |
| metadata | {"author":"Salah-XD","version":"1.0"} |
Use this skill when you need to:
DO NOT use this skill for employer branding, careers page copy, or team charters. This is for the internal culture definition document.
CULTURE IS NOT WHAT YOU SAY — IT IS WHAT YOU DO REPEATEDLY. A CULTURE DOCUMENT IS ONLY VALUABLE IF IT DESCRIBES REAL BEHAVIORS, NOT ASPIRATIONAL PLATITUDES.
Uncover the real culture before documenting it.
| Input | What to Ask | Default |
|---|---|---|
| Business stage | "How old is the business and how many people?" | Early stage, 1-5 people |
| Current values | "Do you have stated values? If yes, what are they?" | No formal values |
| What you reward | "What behavior gets praised or rewarded in your business?" | No default |
| What frustrates you | "What behavior drives you crazy in team members or partners?" | No default |
| Heroes | "Describe someone who exemplifies what your business stands for." | No default |
| Decision filter | "When you make a hard business decision, what principle guides you?" | No default |
## Culture Reality Check
Answer honestly — not what you aspire to, but what is true today:
1. What behavior gets someone promoted or re-hired here?
2. What behavior gets someone fired or not renewed?
3. When there is a conflict between speed and quality, which wins?
4. When there is a conflict between the customer and the team member, which wins?
5. What would a new hire observe about how we work in their first week?
GATE: Complete the discovery before writing the culture document.
Articulate 3-5 core values with behavioral definitions.
For each value, define three layers:
## Our Values
### Value 1: [Name — e.g., "Own It"]
**What it means:** [One sentence definition]
**What it looks like:**
- [Specific observable behavior — e.g., "You flag problems early instead of hoping they go away"]
- [Specific behavior — e.g., "You say 'I will handle that' and follow through without being reminded"]
- [Specific behavior]
**What it does NOT look like:**
- [Anti-behavior — e.g., "Blaming external factors when something goes wrong"]
- [Anti-behavior — e.g., "Waiting to be told what to do"]
**How we assess it:**
- In hiring: [Question or scenario that tests this value]
- In reviews: [Observable evidence of this value]
Every value must pass these tests:
These are not values — they are generic expectations:
Instead, describe the SPECIFIC version: "We ship fast and fix forward" is more useful than "Innovation."
GATE: Present values for review before building the full document.
Create the complete culture document.
# [Business Name] Culture
**Last updated:** [Date]
---
## Who We Are
[2-3 paragraph narrative: What this business stands for, who we serve, and how we approach our work. Write in first person plural. Be specific and honest.]
## Our Values
### 1. [Value Name]
[Full definition with behaviors and anti-behaviors — from Phase 2]
### 2. [Value Name]
[Full definition]
### 3. [Value Name]
[Full definition]
## How Culture Shows Up Daily
### How We Communicate
[Specific norms — e.g., "We default to async. We write things down. We assume good intent in written messages."]
### How We Make Decisions
[Decision framework — e.g., "We move fast with 80% certainty. We do not wait for perfect information."]
### How We Give Feedback
[Feedback norms — e.g., "Directly and promptly. We do not save feedback for quarterly reviews."]
### How We Handle Mistakes
[Error culture — e.g., "We own mistakes publicly, learn from them, and move on. We do not punish honest errors."]
## Our Rituals
| Ritual | Frequency | Purpose |
|--------|-----------|---------|
| [e.g., Monday priorities share] | Weekly | Alignment and accountability |
| [e.g., Friday wins thread] | Weekly | Celebration and momentum |
| [e.g., Quarterly retrospective] | Quarterly | Continuous improvement |
## Who Thrives Here
This is a great place for people who:
- [Trait — e.g., "Want ownership, not hand-holding"]
- [Trait — e.g., "Communicate proactively, especially bad news"]
- [Trait]
This is NOT a great place for people who:
- [Anti-trait — e.g., "Need constant direction and approval"]
- [Anti-trait — e.g., "Avoid difficult conversations"]
- [Anti-trait]
GATE: Present the full document for review.
Make the culture document a living part of the business.