「manifesto」の検索結果

Write a brand manifesto — a bold, belief-driven declaration of what the brand stands for, fights against, and exists to change. Use when the user says "brand manifesto", "manifesto", "what we believe", "brand declaration", "brand belief statement", "rally the team around the brand", "inspire the team", "internal brand document", "culture document", "why we exist statement", "brand credo", "brand creed", or wants to write something that goes beyond a mission statement to express the brand's conviction and worldview.

日本語の概要は準備中です。原文の説明を表示しています。

Patterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.

日本語の概要は準備中です。原文の説明を表示しています。

An editorial-style poster — newsprint paper, dateline, oversized serif headline with a struck-through word and italic accent, a 2-column body block, and 6 numbered sections with annotated pull-quote captions. Reads like a Sunday-paper full-page essay or a thoughtful launch poster. Use when the brief asks for "magazine poster", "editorial poster", "newsprint", "essay layout", or "manifesto".

日本語の概要は準備中です。原文の説明を表示しています。

A personal manifesto: a year of saying yes — the premise, the scenes, the turn, and the meaning that lands. Built as a decision-grade story deck for community, talk audience.

日本語の概要は準備中です。原文の説明を表示しています。

Editorial studio deck template in burgundy / blush / muted-gold palette. Use when users ask for premium manifesto or culture slides with pill tags, large typographic statements, principle cards, and guided keyboard/click navigation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) — including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Ishikawa's 5W2H method, Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists (e.g., "validate this runbook before it goes into rotation", "audit our Confluence wiki for stale and orphaned SOPs").

日本語の概要は準備中です。原文の説明を表示しています。

Sunday-paper 风格, 大字 serif headline + 双栏正文 + 编号 sections

日本語の概要は準備中です。原文の説明を表示しています。

把 outline 1:1 铸成色块大字宣言 deck, 原文不动只做美化。三档主题 black / red / yellow

日本語の概要は準備中です。原文の説明を表示しています。

Reveal marked-up text word by word as scroll progress advances, while preserving semantic inline links, emphasis, responsive line wrapping, and reduced-motion readability. Use for headlines, quotes, manifestos, product statements, onboarding messages, or editorial passages where scrolling should pace comprehension rather than simulate typing.

日本語の概要は準備中です。原文の説明を表示しています。

A 1970s European editorial poster in motion — a red rule draws across, a giant tilted figure drops in, a three-line headline rises line-by-line, an italic serif standfirst fades.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when someone wants to articulate, explore, or document their personal worldview, values, or philosophy. Triggers on "articulate my values", "figure out what I believe", "document my philosophy", "write a manifesto", "define my leadership philosophy", "explore my beliefs". Surfaces beliefs through systematic interrogation, identifies tensions, and generates narrative outputs.

日本語の概要は準備中です。原文の説明を表示しています。

Provider-independent production workflow for AI agents creating brand launch films, product reveal videos, manifesto films, campaign hero films, website hero videos, investor/customer launch assets, and social cutdowns. Use when planning, scripting, generating, editing, reviewing, or delivering launch films that must align strategy, claims, brand voice, visual direction, product proof, accessibility, compliance, and multi-platform delivery.

日本語の概要は準備中です。原文の説明を表示しています。

World-class brand positioning expertise combining David Ogilvy's direct response wisdom, Emily Heyward's obsessive brand strategy (Red Antler), and Al Ries/Jack Trout's positioning classics. This skill answers: "What space do we own in the customer's mind, and why does it matter?" Brand isn't what you say about yourself - it's what others say when you're not in the room. Positioning isn't about creativity - it's about claiming territory in an overcrowded mind. Use when "brand positioning, positioning statement, brand strategy, category design, competitive positioning, how should we position, brand differentiation, value proposition, what makes us different, brand platform, brand values, brand personality, brand promise, brand manifesto, tagline, unique selling proposition, usp, category creation, own a word, mind share, brand, positioning, strategy, differentiation, category, competitive, values, identity" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/. For a short-form post, see linkedin-post. For the newsletter, see newsletter-writer. For improving an existing draft, see copy-review.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the GAO Agile Assessment Guide (GAO-24-105506, 2023). Use for assessing and managing Agile software development in federal programs: the Agile Manifesto and framework family (Scrum, Kanban, XP, SAFe, DA, DSDM, Lean, DevOps); the three adoption perspectives (team dynamics, program operations, organization environment); requirements decomposition (epics, features, user stories, INVEST, MoSCoW, definition of done); Agile-aware federal contracting (FAR, modular contracting, SOO/PWS/SOW, product owner vs. COR); program monitoring and control (WBS, cost, schedule, EVM at the feature level); Agile metrics (velocity, lead/cycle time, CFD, burn charts); and the auditor's key-question bank. Oversight- and acquisition-oriented: it tells you how to *assess and govern* Agile programs, not how to code. Thin on hands-on engineering practice, deep cost/schedule checklists (see gao-cost, gao-schedule), and any non-US-federal context.

日本語の概要は準備中です。原文の説明を表示しています。