From concept-brief-plugin
Guides a section-by-section Direction Document conversation for a Kerten Hospitality hotel management proposal. Activates when a user begins discussing a new property, deal, or concept brief. Manages a running artifact that records confirmed sections.
How this skill is triggered — by the user, by Claude, or both
Slash command
/concept-brief-plugin:concept-briefingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Drive a structured, conversational Direction Document session for a Kerten Hospitality hotel management proposal. Work through sections one at a time: propose content, confirm with the user, write to the artifact, advance. The artifact is the single record of everything decided — downstream pipeline agents are driven from it with no further human input.
assets/concept-brief-template.mdreferences/deck-examples/INDEX.mdreferences/deck-examples/cloud7-casablanca-richbond.mdreferences/deck-examples/cloud7-casadora.mdreferences/deck-examples/cloud7-hotel-athens.mdreferences/deck-examples/cloud7-hotel-residence-arlberg.mdreferences/deck-examples/cloud7-hotel-residence-jumeirah.mdreferences/deck-examples/cloud7-hotel-residence-unaizah.mdreferences/deck-examples/cloud7-jax-district.mdreferences/deck-examples/cloud7-residence-istanbul-bomonti.mdreferences/deck-examples/cloud7-residence-jeddah.mdreferences/deck-examples/cloud7-zanzibar.mdreferences/deck-examples/thh-al-ain.mdreferences/deck-examples/thh-haritash.mdreferences/deck-examples/thh-istanbul.mdreferences/deck-examples/thh-la-voglina.mdreferences/deck-examples/thh-lisno.mdreferences/deck-examples/thh-marrakech.mdreferences/deck-examples/thh-olaya-direction1.mdreferences/deck-examples/thh-olaya-direction2.mdDrive a structured, conversational Direction Document session for a Kerten Hospitality hotel management proposal. Work through sections one at a time: propose content, confirm with the user, write to the artifact, advance. The artifact is the single record of everything decided — downstream pipeline agents are driven from it with no further human input.
Before beginning, check for an existing artifact in the current working directory:
concept-brief-[slugified-property-name].mdconcept-brief-*.md files and ask if the user is resuming oneassets/concept-brief-template.md to concept-brief-[slugified-property-name].md and begin from Step 1File name: concept-brief-[slugified-property-name].md
Example: "Dubai Marina Residences" → concept-brief-dubai-marina-residences.md
Location: current working directory
After each confirmed section: append the section to the end of the file. Never overwrite or modify already-confirmed sections.
After writing: tell the user: "Saved to concept-brief-[name].md" and immediately advance to the next step.
Repeat this loop for every section:
If there is not enough information to make a meaningful proposal for a field, ask one targeted question to unblock — then propose.
Purpose: Establish the factual foundation of the property before any creative or strategic work begins.
| Field | Description |
|---|---|
| Property name | Full name or working title of the property |
| Location | City, country, and neighbourhood or district if known |
| Keys | Number of hotel rooms. If unknown, record as TBD |
| Owner | Owner's name and company or entity |
| Positioning tier | Budget / Midscale / Upper Midscale / Upscale / Upper Upscale / Luxury |
| Brand fit hypothesis | Which Kerten brand is being considered and the initial rationale |
Gather fields through conversation — one question at a time, not a list. For Brand Fit Hypothesis: propose based on positioning tier and location rather than waiting for the user to volunteer it. Read references/kh-brands.md to inform the proposal; if the tier and location clearly point to one brand, name it and explain why in one sentence. If there is genuine ambiguity, surface both and ask the user to steer. Scan references/deck-examples/INDEX.md to identify past brand selections in similar market contexts — use this to strengthen or challenge the hypothesis.
Artifact format:
## Property Metadata
- **Property name:** [value]
- **Location:** [value]
- **Keys:** [value]
- **Owner:** [value]
- **Positioning tier:** [value]
- **Brand fit hypothesis:** [value]
Purpose: A single sentence capturing why Kerten is the right operator for this property and what the winning angle is. Everything downstream should be traceable back to it.
Read references/kh-brands.md if not already in context. Synthesise from Step 1 and any additional context in the conversation. A strong thesis names the specific Kerten brand, the market gap or opportunity, the segment or location context, and the owner alignment or deal rationale. Do not make a generic claim about Kerten's capabilities — push toward specificity at every iteration.
Weak: "Kerten brings lifestyle hospitality expertise to this market." Strong: "Cloud 7's tech-forward lifestyle positioning fills a gap in Dubai Marina's midscale segment, where the owner's investment-focused priorities align with Kerten's asset-light management model."
If any of the four elements (brand, gap, segment, owner alignment) are missing, point out what is absent and propose a revision that adds it.
Artifact format:
## Positioning Thesis
[One sentence]
Read references/sections/03-concept-direction.md for field definitions, sub-section guidance, and quality bar.
Read references/deck-examples/INDEX.md if not already in context; identify the 1–2 examples closest to the current brand and market type; load those full files as pattern reference for Vision and Pillars proposals.
Read references/sections/04-owner-context.md for the three-input flow: relationship intelligence intake, web research, and archetype matching.
Read references/kh-owner-archetypes.md to identify the owner's primary archetype after intake and research are complete.
Use web search to research the owner or developer — company background, portfolio, track record, and any public statements on investment strategy.
Read references/sections/05-key-messages.md for proposal approach and quality bar.
Key Messages are derived entirely from the confirmed Owner Context (Step 4) — do not begin this step until Step 4 is saved to the artifact.
Read references/sections/06-experience-inventory.md for sub-section guidance and quality bar.
Read references/kh-fnb-brands.md to match F&B brands to this property — do not propose F&B concepts without consulting this first.
Do not begin this step until Step 3 (Concept Direction) is confirmed.
Steps 7–15 will be added as subsequent sections are built out.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub shaheerairaj/kh-marketplace --plugin concept-brief-plugin