Business & Operations

Standardized cost-estimation framework for great_cto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.

Use when navigating organizational alignment — stakeholder mapping, influence analysis, coalition building, decision archaeology, cross-functional alignment, executive buy-in, or any situation where the path to a decision runs through multiple people with different interests. Produces a stakeholder alignment strategy, not a RACI matrix.

Use when building product strategy, roadmaps, or strategic plans — vision articulation, strategic bet definition, roadmap sequencing, resource allocation, portfolio planning, or quarterly/annual planning. Encodes bet-sizing, option-value sequencing, strategic tension surfacing, and explicit deprioritization. Produces a strategy document, not a feature backlog.

Use when designing pricing strategy, packaging tiers, monetization models, or evaluating pricing changes — pricing model selection, willingness-to-pay analysis, competitive pricing maps, package architecture, freemium conversion, usage-based pricing design, or price change impact assessment.

Use when building product positioning, crafting strategy narratives, preparing stakeholder pitches, writing launch narratives, or constructing the 'why now' story for a product or initiative. Encodes Narrative Arc Construction, April Dunford-inspired Positioning, Why Now analysis, Audience Adaptation, Evidence-Narrative Integration, Objection Anticipation, Competitive Narrative Analysis, and Narrative Testing. Produces a Strategic Narrative Document.

Use when planning a product launch, market entry, or GTM strategy — segment selection, channel strategy, launch sequencing, pricing validation, competitive positioning, or launch readiness assessment. Encodes wedge identification, channel unit economics, launch gating, and failure criteria. Produces a GTM strategy document, not a launch checklist.

--- name: competitive-analysis description: Analyze competitors with feature comparison matrices, positioning analysis, and strategic implications. Use when researching a competitor, comparing product capabilities, assessing competitive positioning, or preparing a competitive brief for product strategy. ---

Generate a complete subcontract from a firm's template, awarded bid, and project specs. Outputs a Word document. Triggers: 'subcontract', 'sub agreement', 'write contract', 'draft subcontract'. Requires awarded bid.

Draft RFIs and manage the ambient issue registry. Reviews issues surfaced by other skills, escalates to formal RFIs. Triggers: 'draft RFI', 'write RFI', 'drawing conflict', 'review issues', 'issue queue'.

Use this skill for any task involving Thai tax invoices, receipts, quotations, or withholding-tax certificates. Trigger whenever the user asks to: draft a Thai tax invoice (ใบกำกับภาษี), receipt (ใบเสร็จ), quotation (ใบเสนอราคา), credit/debit note (ใบลดหนี้/ใบเพิ่มหนี้), or WHT certificate (ภ.ง.ด.3/53). Also trigger for requests like "ออกใบกำกับภาษี", "ใบเสร็จ", "ใบเสนอราคา", "Thai tax invoice", "VAT 7%", "ภาษีหัก ณ ที่จ่าย", or any variation. If the context involves Thai accounting documents...

Use this skill for any task involving Thai customer service messaging — replies, apologies, status updates, refund/return scripts, and auto-replies on LINE OA, Facebook Page, Shopee, Lazada, Instagram DM, TikTok Shop, and similar channels. Trigger whenever the user asks to: reply to a Thai customer, draft an apology, write a refund or return message, write an auto-reply, de-escalate an angry customer, or send a shipping/status update in Thai. Also trigger for requests like "ตอบลูกค้า", "reply...

Research and draft a response to a GitHub issue or question from an external contributor.

One-shot planning format. Use for feature planning, task breakdown, sprint planning, implementation plans. Format: Goal / Steps / Risks / Done-when. Does not persist.

Use when analyzing strengths/weaknesses/opportunities/threats, strategic planning, decision-making support, problem diagnosis, or when user mentions 'SWOT', '优劣势分析', '战略分析', '机会威胁', '态势分析', '战略规划', '竞品分析', '技术选型', '方案对比', '风险评估', '项目立项', '决策支持'.

MUST use after prompt-enhancer. Create implementation plan with MECE decomposition, dependency analysis, risk assessment, and mandatory plan-review.

Use when executing iterative tasks, continuous improvement, quality assurance, process optimization, or when user asks to 'apply PDCA', 'iterate and improve', 'continuous improvement cycle', 'plan-do-check-act'.

Use when user requests complex systems involving multiple modules or subsystems - like "build a XX system", "design XX architecture", or "implement XX with multiple features". Triggers to prevent over-engineering before validating core assumptions.

MUST use for ANY user request. This is a rigid requirement that applies to all tasks and conversations.

Use when facing complex problems requiring innovative solutions, when conventional approaches fail, when breaking down assumptions, or when user asks to 'think from first principles', 'get to the root', 'fundamentally rethink', 'what's the essence', 'strip away assumptions'.

Decision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.

Audits AZIMUTH's coverage completeness. Cross-references what SKILL.md claims to handle against what reference, diagnostic, and domain-policy files actually cover. Identifies thin coverage, missing domains, and structural inconsistencies. Run before major version planning.

Plan weekly P-Tasks with in-repo task triage and overplanning challenge

Build a persona-grounded user journey map for a product flow

Pressure-test a document (PRD, strategy, pitch, positioning) against your product context. Finds gaps, weak logic, and unvalidated assumptions.