Open Source Contribution Guide Architect

Turn scattered inputs into a review-ready Open Source Contribution Guide Architect.

Important work should not start with an ungrounded chat prompt. Open Source Contribution Guide Architect gives Open Source Program Office a repeatable way to turn authorized source material into a structured decision pack: evidence is labeled, open questions remain visible, and every next step has an accountable human owner.

What you can produce

• Repository contribution guide
• Contributor journey map
• Issue and pull request requirements
• Maintainer review checklist

The before-and-after

Before: Important context lives across notes, drafts, spreadsheets, messages, policies, or interviews. Teams debate what is known, what is assumed, and who needs to decide.

After: You have a shared, review-ready artifact centered on Repository contribution guide, with explicit inputs, trade-offs, missing evidence, and an approval-ready next step.

Why this skill earns a place in your workflow

Uses supplied repository context to map contributor personas, contribution types, tooling prerequisites, review gates, and maintenance ownership into one coherent guide.

Use it when

• You need to convert buyer-provided context into a reusable operating artifact.
• You want assumptions, unknowns, and contradictory inputs surfaced before a team acts.
• You need one clear version of the work for cross-functional review and accountable approval.

How it works

1. Provide the authorized context, goal, constraints, and decision owner.
2. Run the workflow to build an evidence ledger, required deliverables, options, and open questions.
3. Review the output with the accountable human, verify claims, and decide whether to implement the next step.

Built for thoughtful teams, not autopilot

This is an instruction-only SKILL.md workflow. It does not log in, browse private systems, edit records, send messages, publish content, run commands, or execute transactions. It is designed to improve the quality and repeatability of team thinking—not to bypass ownership or professional judgment.

Known limitations

The skill drafts informational documents from buyer-provided materials; maintainers must verify technical, licensing, governance, privacy, and security details before publication. Buyers must verify facts, follow their own policies, and obtain any specialist review required for their context. This skill does not provide legal, financial, privacy, compliance, security, accessibility, or safety determinations.