> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shipstar.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# generate_featurebase_articles

> Kick off generation of Featurebase help-center articles from recent commits

Turns recent shipped work into a set of help-center articles for your Featurebase help center. Background task; returns a pending content record.

The draft is a set of articles for review. Approving it ([`approve_content`](/mcp/lifecycle/approve-content)) creates the articles in the project's connected Featurebase help center — in the collection the schedule chose, else the Featurebase destination's default collection — and only then does the content read "published". A failed delivery (rejected API key, missing collection) keeps the set in review with the error shown in the dashboard.

Featurebase must be connected first: Dashboard → Destinations → Featurebase, with an organization-level API key. [`list_destinations`](/mcp/project/list-destinations) shows `featurebase.connected` and the default collection.

## Arguments

| Name           | Type                                       | Default           | Description                                                                                                                                                                                                    |
| -------------- | ------------------------------------------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `start_date`   | string (ISO-8601)                          | 7 days ago        | Earliest commit timestamp to include.                                                                                                                                                                          |
| `end_date`     | string (ISO-8601)                          | now               | Latest commit timestamp to include.                                                                                                                                                                            |
| `product_name` | string                                     | project name      | Override the product name.                                                                                                                                                                                     |
| `idea`         | object                                     | —                 | Optional `{title, summary}` suggestion for the article(s) to write (e.g. a specific feature to document).                                                                                                      |
| `audience`     | `"technical"` \| `"business"` \| `"mixed"` | project default   | Technical depth of the writing. Omit to use the project's [content guidelines](/guides/content-guidelines) default.                                                                                            |
| `instructions` | string (≤ 2000 chars)                      | project default   | Free-text guidance on scope, tone, or terminology, e.g. `"Don't mention marketing website changes"`. Omit to use the project default.                                                                          |
| `repos`        | string\[]                                  | all tracked repos | Restrict the commit source to these tracked repositories (full names, e.g. `["acme/backend"]`), as listed by [`get_project_context`](/mcp/project/get-project-context). Omit to use every active tracked repo. |
| `seed`         | boolean                                    | `false`           | **Seed mode** — build the initial help center instead of a what-changed set (see below). 300 credits.                                                                                                          |
| `max_articles` | integer (5–30)                             | 20                | Seed mode: upper bound on proposed articles.                                                                                                                                                                   |

## Seed mode

A normal run documents one commit window. When a help center is empty, pass `seed: true` to document the product as it is: Shipstar reads the tracked repositories' README and docs folders (up to 24 markdown files) plus the last six months of commits, lists what is already in the Featurebase help center, and asks for an outline of 3–6 collections and up to `max_articles` articles — skipping titles that already exist. The articles are then written in batches and assembled into one reviewable set, grouped by collection.

On approve, each article is filed under its collection; collections that don't exist yet are created in the help center. The set-level collection (schedule or default) only applies to articles without one. Seed mode is meant as a one-off; run it again later and it proposes only topics the help center doesn't cover yet.

## Returns

```json theme={null}
{ "content_id": "...", "status": "pending" }
```

Poll [`get_content_status`](/mcp/lifecycle/get-content-status), then read the draft with [`get_content_draft`](/mcp/lifecycle/get-content-draft) and approve it with [`approve_content`](/mcp/lifecycle/approve-content). Once delivered, the content's metadata carries one entry per created article (`article_id`, `url`) under `featurebase.articles`.

## Example prompts

> "Write Featurebase help articles for everything we shipped this sprint."

> "Turn the last two weeks of commits into how-to articles for our help center."

> "Our Featurebase help center is empty — seed it from the repo docs, at most 15 articles."