confluence
Skill4 starsChanged 3 months agoMITView on GitHub
Placeholder workflow guidance for repos that use Confluence as a durable documentation surface; use when drafting, updating, promoting, or reviewing project overview, architecture, feature, roadmap, milestone, proposal, standard-summary, or completed-specification Confluence pages. Does not assume live Confluence API access unless the repo declares it.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- DaeSeokSong/oh-my-ouroborostheir own version, first seen Nov 1, 2026
- PixiBixi/claude-skillstheir own version, first seen Oct 25, 2026
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- justmiles/skillstheir own version, first seen Oct 20, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use figma and prd.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillfigma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
Also in 3 projects that use this
GitHubSkillprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- SpillwaveSolutions/confluence-skill★ 64same name
- spmtitsolution/OpenBA-Kit★ 38same name
- G1Joshi/Agent-Skills★ 15same name
- Alexander-Tyagunov/magician★ 14same name
- arfar-x/agent-skills★ 14same name
- tvremix/claude-plugin★ 14same name
- odyssey4me/agent-skills★ 13same name
- flurdy/agent-skills★ 9same name
- ThilinaTLM/agent-skills★ 4same name
- DaeSeokSong/oh-my-ouroboros★ 3same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- architecture-doc-builderSkill
- conformanceSkill
- doc-checkSkill
- feature-doc-builderSkill
- gh-issueSkill
- gh-stackSkill
- gh-wikiSkill
- handoffSkill
- jiraSkill
- pr-builderSkill
- proposal-builderSkill
- pr-reviewSkill
- psqlSkill
- qa-testingSkill
- spec-builderSkill
- spec-drivenSkill
- sqlcmdSkill
- standard-builderSkill
- worktreeSkill
- zazz-boardSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when a repo's AGENTS.md declares Confluence as the durable surface for project knowledge or completed specifications.
- Distinctive: line 12
Use repo-declared Confluence spaces, page naming, ownership, and update processes.
- Distinctive: line 16
Read AGENTS.md and confirm Confluence is the declared source of truth for the artifact type you are touching.
- Distinctive: line 22
Read the current page or repo pointer before drafting changes.
- Distinctive: line 23
If access, naming, or responsibility is unclear, ask the responsible human instead of inventing a page.
- Very specific: line 27
Keep local working specifications under <DOCS_ROOT>/specifications/.
- Very specific: line 29
Do not put RUN_LOG files, QA notes, handoffs, recovery notes, evidence captures, or scratch analysis into durable Confluence pages.
- Distinctive: line 33
Do not use Confluence as public user-facing documentation unless the repo explicitly says that is its product-doc surface.
- Very specific: line 35
If a contract changes during implementation, update the specification body and Implementation And Review Change Log first.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Confluence Skill
Use this skill when a repo's AGENTS.md declares Confluence as the durable surface for
project knowledge or completed specifications.
This is a placeholder workflow skill. It does not provide a live Confluence integration. Use repo-declared Confluence spaces, page naming, ownership, and update processes.
Startup Sequence
- Read
AGENTS.mdand confirm Confluence is the declared source of truth for the artifact type you are touching. - Identify the artifact type: project overview, architecture, feature requirements, roadmap, milestone, proposal outcome, completed specification, or standards summary.
- Find the Confluence space, parent page, naming convention, and update authority declared by the repo.
- Read the current page or repo pointer before drafting changes.
- If access, naming, or responsibility is unclear, ask the responsible human instead of inventing a page.
Rules
- Keep local working specifications under
<DOCS_ROOT>/specifications/; promote or mirror final implemented specs to Confluence only when the repo declares that policy. - Do not put RUN_LOG files, QA notes, handoffs, recovery notes, evidence captures, or scratch analysis into durable Confluence pages.
- Preserve stable links back to source PRs, merge commits, tracker records, and governing specs when available.
- Do not use Confluence as public user-facing documentation unless the repo explicitly says that is its product-doc surface.
- If a contract changes during implementation, update the specification body and
Implementation And Review Change Logfirst; update Confluence after the durable outcome is accepted or merged.
Output
Produce either:
- a Confluence page update through the repo-declared workflow, or
- a concise draft/pointer that a human can apply when live Confluence access is unavailable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.