Results for “heading-hierarchy”

15 skills
neekware
chro-advisor
People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management.
0 · bundle
heath-gtm
heath-no-fluff
heath-no-fluff
0
dracounion
goal-hierarchy-design
当需要将模糊的长期愿景转化为可执行的日常行动,以提升专注力和生活掌控感时
11 · bundle
landonschropp
outline
Use when content or notes need organizing into a structured, hierarchical outline
1
snoodleboot-io
state-management-architecture
The single highest-leverage decision is recognizing that most of what teams call
2
intense-visions
harness-strategy
Harness Strategy
18 · bundle
bog5d
handoff
Handoff
0
alirezarezvani
chro-advisor
Provides people strategy and operational HR frameworks for hiring, compensation, org design, and culture that scales.
20.4k · bundle
intense-visions
db-covering-index
Covering Indexes
18 · bundle
owl-listener
critique-visual-hierarchy
Analyze a screen's visual hierarchy by evaluating entry point, eye flow, weight distribution, and emphasis, then provide actionable fixes.
1.7k
neekware
chief-of-staff
C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically.
0 · bundle
snoodleboot-io
grafana-dashboard-design
**Level 1: Executive Dashboard**
2
deanpeters
altitude-horizon-framework
Diagnose the PM-to-Director transition using altitude (scope) and horizon (time) axes, identify transition zones, and apply the Cascading Context Map when organizational direction is vague.
5.6k · bundle
dracounion
holonic-alignment
当寻求个人行动或项目在更宏大系统中的意义,或需要将日常工作与长远价值连接时
11 · bundle
testdouble
explanation-guidance
Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.
218