Results for “business”

Build the PRINCE2 Initiating a Project pack: project initiation documentation, business case, project plan, controls, management approaches, product descriptions, and baseline decisions.

Write clear design rationale that connects decisions to user needs, business goals, and principles.

Prepare PRINCE2 Managing a Stage Boundary material: end stage report, next stage plan, updated business case, updated project plan, lessons, risks, issues, and exception plan if needed.

Generate UK/EU GDPR compliance documents — privacy policies, cookie policies, DPIAs, ROPA, DSAR responses, data breach notifications, and consent forms. Use when a business needs GDPR documentation, data protection policies, or privacy compliance.

Create professional Marp presentation slides with 7 beautiful themes (default, minimal, colorful, dark, gradient, tech, business). Use when users request slide creation, presentations, or Marp documents. Supports custom themes, image layouts, and "make it look good" requests with automatic quality improvements.

Turns any long-running domain (business, relationships, health, career, learning, investing) into a local knowledge project with four layers, source tags, immutable snapshots, and a concept library that learns patterns over time.

Produces HTML-first visual design deliverables such as interactive prototypes, slide decks, motion demos, infographics, dashboards, landing pages, whitepapers, changelogs, business cards, social covers, and brand systems, with optional export to MP4, GIF, PPTX, PDF, or SVG.

Drafts SEC Form 8-K current reports with item-accurate narratives, exhibit indexing, and EDGAR-ready formatting. Use when a public company must disclose a reportable event (material agreement, acquisition, personnel change, Reg FD disclosure) or file a current report within four business days. Trigger on "Form 8-K", "current report", "8-K filing", "EDGAR", "Item 1.01", "Item 2.01", "Item 5.02", "Reg FD".

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.