Problem
99problems currently supports GitHub, GitLab, Jira, and Bitbucket (Cloud and Datacenter), but not Confluence.
Teams that store architecture/decision context in Confluence cannot retrieve that context through 99problems, which limits cross-system task preparation for humans and agents.
Design
Implement Confluence Cloud provider (selfhosted will follow in future issue) using the existing conversation schema:
- map each Confluence page as an issue-like conversation,
- support raw CQL search via
-q,
- support page fetch by Confluence page ID.
Confluence v1 boundaries:
- Cloud only,
- no PR mode (
--type pr rejected),
--repo reused as Confluence space key,
--url required for tenant base URL.
Scope
- Add source adapter under
src/source/confluence/.
- Wire
confluence platform selection in get and config validation.
- Add Confluence env auth mapping (
CONFLUENCE_TOKEN, CONFLUENCE_ACCOUNT_EMAIL).
- Implement raw CQL search and page ID fetch.
- Hydrate body/comments/basic links using existing payload flags.
- Update docs/examples and skill references.
Boundary
- No Confluence Data Center support in this issue.
- No new output schema/content-kind in this issue.
- No shorthand query DSL translation;
-q is CQL pass-through.
Acceptance Criteria
99problems get --platform confluence --url <tenant-url> --repo <space> -q "<cql>" works.
99problems get --platform confluence --url <tenant-url> --id <page-id> --type issue works.
--type pr on Confluence returns clear usage error.
--no-comments, --no-links, and --no-body are respected.
- Comments/links hydration failures are best-effort and do not fail core page retrieval.
- Existing providers remain unaffected.
Context
This adds documentation knowledge retrieval to 99problems while preserving the existing output contract and CLI ergonomics.
References:
Problem
99problemscurrently supports GitHub, GitLab, Jira, and Bitbucket (Cloud and Datacenter), but not Confluence.Teams that store architecture/decision context in Confluence cannot retrieve that context through
99problems, which limits cross-system task preparation for humans and agents.Design
Implement Confluence Cloud provider (selfhosted will follow in future issue) using the existing conversation schema:
-q,Confluence v1 boundaries:
--type prrejected),--reporeused as Confluence space key,--urlrequired for tenant base URL.Scope
src/source/confluence/.confluenceplatform selection ingetand config validation.CONFLUENCE_TOKEN,CONFLUENCE_ACCOUNT_EMAIL).Boundary
-qis CQL pass-through.Acceptance Criteria
99problems get --platform confluence --url <tenant-url> --repo <space> -q "<cql>"works.99problems get --platform confluence --url <tenant-url> --id <page-id> --type issueworks.--type pron Confluence returns clear usage error.--no-comments,--no-links, and--no-bodyare respected.Context
This adds documentation knowledge retrieval to 99problems while preserving the existing output contract and CLI ergonomics.
References: