From ccb2f9464f1b7712e2fe1c01b7cdb45d451195d1 Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Sun, 21 Sep 2025 23:00:41 -0400 Subject: [PATCH 1/7] Draft of Project manager process documents --- docs/octoacme-execution-and-tracking.md | 40 +++++++++ docs/octoacme-project-initiation.md | 43 ++++++++++ docs/octoacme-project-management-overview.md | 46 +++++++++++ docs/octoacme-project-planning.md | 43 ++++++++++ docs/octoacme-release-and-deployment.md | 38 +++++++++ ...etrospective-and-continuous-improvement.md | 33 ++++++++ docs/octoacme-risks-and-communication.md | 42 ++++++++++ docs/octoacme-rols-and-personas.md | 81 +++++++++++++++++++ 8 files changed, 366 insertions(+) create mode 100644 docs/octoacme-execution-and-tracking.md create mode 100644 docs/octoacme-project-initiation.md create mode 100644 docs/octoacme-project-management-overview.md create mode 100644 docs/octoacme-project-planning.md create mode 100644 docs/octoacme-release-and-deployment.md create mode 100644 docs/octoacme-retrospective-and-continuous-improvement.md create mode 100644 docs/octoacme-risks-and-communication.md create mode 100644 docs/octoacme-rols-and-personas.md diff --git a/docs/octoacme-execution-and-tracking.md b/docs/octoacme-execution-and-tracking.md new file mode 100644 index 0000000..744548c --- /dev/null +++ b/docs/octoacme-execution-and-tracking.md @@ -0,0 +1,40 @@ +# OctoAcme — Execution & Tracking + +## Purpose +Guidance for managing day-to-day execution and tracking progress toward project milestones. + +## Team Rhythm +- Daily standups (15 min) — focus on progress, blockers, dependencies +- Weekly delivery sync — show progress, updates, and flagged risks +- Demo/Review at the end of each sprint or milestone + +## Workflows +- Use the project board (e.g., GitHub Projects) with columns: Backlog, Ready, In Progress, In Review, QA, Done +- Pull Request workflow: + - Small PRs (<= 400 lines when possible) + - Include issue link and acceptance criteria in PR description + - Run automated tests and linting in CI before requesting review + - Require at least one approval before merging (or team-defined policy) + +## Quality & Testing +- Unit tests for new logic +- Integration tests where applicable +- End-to-end smoke tests for critical flows before release +- Security scanning in CI +- Manual QA for feature acceptance when needed + +## Reporting & Metrics +- Track velocity and burndown +- Monitor success metrics identified in the Project One-pager +- Use dashboards for key signals (errors, latency, usage) + +## Blocker Escalation +- Level 1: Team-level triage in daily standup +- Level 2: PM escalates to Product Lead and dependent teams +- Level 3: Sponsor-level escalation for business-impacting issues + +## Execution Checklist +- [ ] Branching and PR conventions documented in repo +- [ ] CI configured for tests and lint +- [ ] Regular demos scheduled +- [ ] Risk register updated weekly diff --git a/docs/octoacme-project-initiation.md b/docs/octoacme-project-initiation.md new file mode 100644 index 0000000..925ccb3 --- /dev/null +++ b/docs/octoacme-project-initiation.md @@ -0,0 +1,43 @@ +# OctoAcme — Project Initiation Guide + +## Purpose +Define the initial steps to validate and authorize work, align stakeholders, and create a lightweight plan. + +## When to use +Whenever a new project idea or feature proposal is ready to be explored. + +## Goals +- Confirm business need and measurable outcome +- Identify stakeholders & champions +- Define success criteria and initial timeline +- Decide go/no-go for planning + +## Minimum Deliverables +- Project One-pager (Problem, Goal, Success Metrics) +- Stakeholder list & communication plan +- High-level timeline and key milestones +- Initial risk list +- Resource needs (team roles, rough effort estimate) + +## Project One-pager Template +- Project name: +- Problem statement: +- Objective / Goal (SMART): +- Success metrics: +- Primary stakeholders: +- Suggested timeline / milestones: +- Quick risks & dependencies: +- Proposed team / roles: + +## Initiation Checklist +- [ ] One-pager completed and reviewed by Product Lead +- [ ] Sponsor / Stakeholder alignment (email or meeting) +- [ ] Decision: Approve to move into planning? +- [ ] Create repo or project board skeleton +- [ ] Add initial artifacts to repo (docs/ or .copilot/) + +## Decision Gate +Move to planning when: +- Success metrics are clear +- Stakeholders agree on priority +- Team availability is confirmed diff --git a/docs/octoacme-project-management-overview.md b/docs/octoacme-project-management-overview.md new file mode 100644 index 0000000..3277dfe --- /dev/null +++ b/docs/octoacme-project-management-overview.md @@ -0,0 +1,46 @@ +# OctoAcme Project Management Overview + +## Purpose +Provide a concise, shareable introduction to how OctoAcme runs projects so new teammates can quickly understand our approach, roles, and key artifacts. + +## Scope +Applies to all cross-functional projects that deliver product features, services, or integrations. + +## Principles +- Customer-first: prioritize customer value and usability. +- Iterative delivery: deliver small, testable increments. +- Clear ownership: each project has a named Project Manager (PM) and Product Lead. +- Data-informed decisions: measure impact and iterate based on evidence. +- Psychological safety: encourage feedback and learning. + +## Core Roles +- Project Manager (PM): coordinates delivery, schedules, risk, communications. +- Product Manager (PdM): defines outcomes, prioritizes backlog, and measures success. +- Developers: implement features, collaborate on design and testability. +- QA/Testing: validate quality and acceptance criteria. +- Stakeholders: provide inputs and approvals. + +## Key Artifacts +- Project Charter / One-pager +- Roadmap and Release Plan +- Sprint/Iteration Backlog +- Acceptance Criteria & Definition of Done +- Risk Register +- Retrospective notes and action items + +## Lifecycle (high-level) +1. Initiation: problem statement, stakeholders, high-level timeline. +2. Planning: scope, resources, milestones, dependencies. +3. Execution: build, test, review, iterate. +4. Release: deploy, verify, announce. +5. Close & Retrospective: capture learnings and next steps. + +## Communication Cadence +- Weekly sync between PM + PdM +- Twice-weekly standups for delivery team (or as agreed) +- Monthly stakeholder updates +- Ad-hoc escalations as needed + +## How to use these docs +- Keep the Project Charter updated in the project repo. +- Add process-specific docs into `.copilot/` if you want Copilot Spaces to use them as context. diff --git a/docs/octoacme-project-planning.md b/docs/octoacme-project-planning.md new file mode 100644 index 0000000..f688868 --- /dev/null +++ b/docs/octoacme-project-planning.md @@ -0,0 +1,43 @@ +# OctoAcme — Project Planning + +## Purpose +Turn an approved initiative into an actionable plan and backlog for delivery. + +## Objectives +- Break work into shippable increments +- Identify dependencies and risks +- Align timelines, releases, and responsibilities + +## Activities +1. Kickoff meeting with stakeholders and delivery team +2. Create prioritized backlog with acceptance criteria +3. Estimate scope (T-shirt sizing or story points) +4. Define Definition of Done (DoD) +5. Identify dependencies and integration points +6. Create release plan and milestone map + +## Backlog Item Template +- Title: +- Description: +- Acceptance criteria: +- Priority: +- Estimate: +- Owner: +- Related docs/links: + +## Sprint / Iteration Planning +- Timebox planning to agreed sprint length +- Pull items that meet DoD and have clear acceptance criteria +- Ensure team capacity is respected + +## Risk & Dependency Management +- Capture in Risk Register: + - ID, Description, Impact, Probability, Owner, Mitigation +- Mark cross-team dependencies in the project board and escalate during weekly syncs + +## Planning Checklist +- [ ] Project kickoff held +- [ ] Backlog prioritized and estimated +- [ ] Release timeline and milestones agreed +- [ ] Definition of Done documented +- [ ] Initial test plan / QA approach drafted diff --git a/docs/octoacme-release-and-deployment.md b/docs/octoacme-release-and-deployment.md new file mode 100644 index 0000000..94af438 --- /dev/null +++ b/docs/octoacme-release-and-deployment.md @@ -0,0 +1,38 @@ +# OctoAcme — Release & Deployment Guide + +## Purpose +Standardize how OctoAcme releases features to production to reduce risk and improve observability. + +## Release Types +- Patch: hotfixes addressing critical production issues +- Minor: incremental features and improvements +- Major: significant functionality or breaking changes + +## Pre-release requirements +- All acceptance criteria met and PRs merged +- Passing CI and security scans +- Release notes drafted +- Rollback / mitigation plan documented +- Smoke tests prepared + +## Deployment Checklist +- [ ] Deployment window scheduled (if needed) +- [ ] Backup or snapshot (if applicable) +- [ ] Deploy to staging and run smoke tests +- [ ] Deploy to production (automated pipeline preferred) +- [ ] Run post-deploy verifications +- [ ] Announce release to stakeholders and support + +## Rollback & Incident Playbook +- If a deployment fails or causes a critical issue: + - Trigger incident response and notify on-call + - Rollback to last known-good release if necessary + - Triage root cause and capture action items + +## Release Notes Template +- Release name / number: +- Date: +- Summary: +- Notable changes: +- Migration steps (if any): +- Known issues: diff --git a/docs/octoacme-retrospective-and-continuous-improvement.md b/docs/octoacme-retrospective-and-continuous-improvement.md new file mode 100644 index 0000000..5d98561 --- /dev/null +++ b/docs/octoacme-retrospective-and-continuous-improvement.md @@ -0,0 +1,33 @@ +# OctoAcme — Retrospective & Continuous Improvement + +## Purpose +Capture learnings and convert them into actionable improvements. + +## When +After each sprint, release, or important milestone. Also after incidents. + +## Structure +- What went well +- What could be improved +- Action items (owner, due date) +- Follow-up on previous action items + +## Running a Retrospective +- Timebox: 45–75 minutes depending on team size +- Use an anonymous idea board if needed to encourage candor +- Prioritize 2–3 top action items to avoid overload + +## Tracking Improvements +- Add action items to the project backlog or issues with clear owners and timelines +- Review outstanding actions in the weekly PM sync + +## Example Action Item Template +- Title: +- Description: +- Owner: +- Due date: +- Success criteria: + +## Continuous Improvement Culture +- Measure impact of action items +- Celebrate improvements and make small, iterative changes diff --git a/docs/octoacme-risks-and-communication.md b/docs/octoacme-risks-and-communication.md new file mode 100644 index 0000000..e9a2799 --- /dev/null +++ b/docs/octoacme-risks-and-communication.md @@ -0,0 +1,42 @@ +# OctoAcme — Risk Management & Communication + +## Purpose +Explain how to identify, manage, and communicate risks and dependencies. + +## Risk Register +Maintain a simple table with: +- ID +- Description +- Impact (High/Med/Low) +- Likelihood (High/Med/Low) +- Owner +- Mitigation plan +- Status + +## Risk Lifecycle +- Identify: during planning and ongoing execution +- Assess: estimate impact and likelihood +- Mitigate: reduced via actions, contingency plans +- Monitor: review at weekly syncs and update status + +## Stakeholder Communication +- Identify stakeholder groups and communication needs (e.g., engineering, sales, support) +- Provide regular updates (weekly or milestone-based) +- Use a single source of truth (project README or release doc) for status + +## Communication Templates +Weekly Status Template: +- Progress this week: +- Next steps: +- Risks & blockers: +- Ask / decisions needed: + +Incident Communication +- Triage summary +- Actions being taken +- Expected timeline +- Post-incident blameless retrospective scheduled + +## Escalation Paths +- Team-level -> PM -> Product Lead -> Sponsor +- For security incidents, follow the security incident runbook and notify Security on-call diff --git a/docs/octoacme-rols-and-personas.md b/docs/octoacme-rols-and-personas.md new file mode 100644 index 0000000..dbbba4f --- /dev/null +++ b/docs/octoacme-rols-and-personas.md @@ -0,0 +1,81 @@ +# OctoAcme Personas + +This document defines typical roles and responsibilities used in OctoAcme project docs and exercises. + +--- + +## Developers + +### Role Summary +Developers design, build, test, and deliver software components. They collaborate with product and project leads to implement features that meet acceptance criteria and quality standards. + +### Responsibilities +- Implement features and fixes to meet acceptance criteria +- Write and maintain tests and documentation +- Participate in design and code reviews +- Assist in estimating and planning work +- Help identify technical risks and propose mitigations + +### Goals +- Deliver reliable, maintainable code +- Reduce cycle time from idea to production +- Maintain high test coverage and observability + +### Typical Communication +- Daily standups and sprint planning +- PR descriptions and code review comments +- Technical design docs when needed + +--- + +## Product Managers + +### Role Summary +Product Managers define what should be built to deliver customer and business value. They own the product vision, prioritize the backlog, and measure outcomes. + +### Responsibilities +- Define problem statements and success metrics +- Prioritize the roadmap and backlog +- Collaborate with stakeholders and engineering on trade-offs +- Validate solutions through user research and metrics + +### Goals +- Maximize customer value and impact +- Make clear, data-driven prioritization decisions +- Ensure product-market fit and usability + +### Typical Communication +- Weekly alignment with PM and engineering leads +- Roadmap updates and stakeholder briefings +- Acceptance criteria and feature specs + +--- + +## Project Managers + +### Role Summary +Project Managers coordinate delivery activities, manage schedules, risks, and communications. They enable the team to deliver on commitments efficiently. + +### Responsibilities +- Create and maintain project plans and timelines +- Manage risks, dependencies, and resource constraints +- Facilitate meetings (kickoff, planning, retrospectives) +- Ensure consistent project documentation and status reporting +- Coordinate cross-team and stakeholder communication + +### Goals +- Deliver projects on time and within scope +- Minimize unplanned work and escalations +- Maintain transparency and alignment across stakeholders + +### Typical Communication +- Weekly status updates and stakeholder reports +- Risk registers and decision logs +- Coordination via project boards and meeting facilitation + +--- + +## How these personas are used in the exercise +- Use these persona definitions to frame scenarios and sample interactions in the Skills Exercise. +- Each persona can be used as a persona prompt for Copilot Spaces to shape role-specific guidance. + From 6c4dee645a66375bdddad3937e351eb8354798b8 Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Mon, 22 Sep 2025 11:02:37 -0400 Subject: [PATCH 2/7] Update steps for the Skills exercise on Copilot Spaces --- .github/steps/1-step.md | 49 +++++++++++++++++++++++++++------------ .github/steps/2-step.md | 44 +++++++++++++++++++++++------------ .github/steps/3-step.md | 43 ++++++++++++++++++++++------------ .github/steps/4-step.md | 46 ++++++++++++++++++++++++++++++++++++ .github/steps/x-review.md | 25 +++++++++++++++----- README.md | 28 +++++++++++----------- 6 files changed, 170 insertions(+), 65 deletions(-) create mode 100644 .github/steps/4-step.md diff --git a/.github/steps/1-step.md b/.github/steps/1-step.md index 10e5155..bc2de55 100644 --- a/.github/steps/1-step.md +++ b/.github/steps/1-step.md @@ -1,27 +1,46 @@ -## Step 1: (replace-me: STEP-NAME) +## Step 1: Create a Copilot Space -(replace-me: OPTIONAL Brief story or scenario to introduce the step) +You've just been hired as a project manager at OctoAcme, a growing tech company. Your team is struggling with scattered project management knowledge - processes are documented in different places, tribal knowledge exists only in people's heads, and new team members have trouble getting up to speed. You've heard about GitHub Copilot Spaces and want to use it to centralize and democratize your team's project management knowledge. -### 📖 Theory: (replace-me: Theory title) +### 📖 Theory: Understanding Copilot Spaces - - +GitHub Copilot Spaces is a collaborative workspace that allows you to ground Copilot's knowledge in your specific context. By creating a dedicated Space, you can: + +- **Centralize knowledge**: Bring together documentation, code, and processes in one place +- **Add contextual sources**: Include repositories, documentation, and other resources that inform Copilot about your work +- **Enable focused conversations**: Use Copilot with deep understanding of your specific domain and processes +- **Scale expertise**: Make tribal knowledge accessible to everyone on your team + +Spaces help transform scattered information into an organized, searchable, and intelligent knowledge base that grows with your team. -(replace-me: Optional theory or background information relevant to this step) +### ⌨️ Activity: Create Your Project Management Copilot Space + +1. Navigate to GitHub Copilot Spaces in your GitHub account +1. Click "Create new Space" or the equivalent option +1. Name your Space: "OctoAcme Project Management Hub" +1. Add a description: "Centralizing and democratizing project management knowledge for the OctoAcme team" +1. Set the Space visibility according to your organization's policies +1. Create the Space + +> [!NOTE] +> If you don't have access to Copilot Spaces yet, you can simulate this step by taking notes on what you would include in your Space setup. -### ⌨️ Activity: (replace-me: Activity title) +### ⌨️ Activity: Add Source Repositories -1. (replace-me: First instruction) -1. (replace-me: Second instruction) -1. (replace-me: Additional instructions as needed) +1. In your newly created Copilot Space, look for "Sources" or "Add Source" section +1. Add this exercise repository as a source: + - Repository URL: `https://github.com/arilivigni/democratize-tribal-knowledge-using-copilot-spaces` + - This gives Copilot access to the project management documentation and processes +1. Wait for the repository to be indexed (this may take a few minutes) +1. Verify the repository appears in your sources list +1. (Optional) If you have other project management repositories or documentation, add them as additional sources
Having trouble? 🤷
-- (replace-me: Troubleshooting tip or hint) -- (replace-me: Additional troubleshooting tips as needed) +- Make sure you have access to GitHub Copilot Spaces (currently in beta/limited access) +- The repository should be publicly accessible for Copilot to index it +- If you can't access Copilot Spaces, you can continue by manually exploring the repository structure and documentation +- Repository indexing can take 5-10 minutes depending on size
diff --git a/.github/steps/2-step.md b/.github/steps/2-step.md index 03208a4..421bed0 100644 --- a/.github/steps/2-step.md +++ b/.github/steps/2-step.md @@ -1,27 +1,41 @@ -## Step 2: (replace-me: STEP-NAME) +## Step 2: Explain the Project Management process docs -(replace-me: OPTIONAL Brief story or scenario to introduce the step) +Now that you have the repository added as a source, it's time to explore OctoAcme's project management processes. All the documentation is stored in the `docs` folder, and you need to understand what processes are currently in place. -### 📖 Theory: (replace-me: Theory title) +### 📖 Theory: Process Documentation Analysis - - +Effective project management relies on well-documented, consistent processes. Documentation serves as the foundation for: +- Onboarding new team members +- Ensuring consistent execution across projects +- Identifying gaps and improvement opportunities +- Scaling practices across growing teams -(replace-me: Optional theory or background information relevant to this step) +When analyzing process documentation, look for: +- Clear step-by-step procedures +- Defined roles and responsibilities +- Decision-making frameworks +- Communication protocols +- Quality gates and checkpoints -### ⌨️ Activity: (replace-me: Activity title) +### ⌨️ Activity: Summarize Project Management Processes -1. (replace-me: First instruction) -1. (replace-me: Second instruction) -1. (replace-me: Additional instructions as needed) +1. Browse to the `docs` folder in this repository +2. Review all the project management process documents +3. Using GitHub Copilot (or manual analysis), create a comprehensive summary +4. In the comments of this issue, provide a summary that includes: + - Overview of the current project management approach + - Key processes documented in the `docs/` folder + - Primary roles and responsibilities mentioned + - Any gaps or areas that seem unclear + +Your summary should be 3-4 paragraphs covering the main processes OctoAcme uses for project management.
Having trouble? 🤷
-- (replace-me: Troubleshooting tip or hint) -- (replace-me: Additional troubleshooting tips as needed) +- Look for files like `project-lifecycle.md`, `roles-responsibilities.md`, `communication-plan.md` in the docs folder +- Focus on understanding the overall workflow rather than memorizing every detail +- If using Copilot, try asking: "Summarize the project management processes in the docs folder"
+ diff --git a/.github/steps/3-step.md b/.github/steps/3-step.md index a732c45..37efd8f 100644 --- a/.github/steps/3-step.md +++ b/.github/steps/3-step.md @@ -1,27 +1,40 @@ -## Step 3: (replace-me: STEP-NAME) +## Step 3: Add a chat mode project management process deep dive -(replace-me: OPTIONAL Brief story or scenario to introduce the step) +Time to create a specialized chat mode that will help you dive deeper into OctoAcme's project management processes. Custom chat modes allow you to focus Copilot's capabilities on specific topics and workflows. -### 📖 Theory: (replace-me: Theory title) +### 📖 Theory: Custom Chat Modes in Copilot Spaces - - +Custom chat modes are specialized conversation contexts that guide Copilot to focus on specific domains, use cases, or expertise areas. They work by: +- Providing domain-specific context and vocabulary +- Establishing conversation patterns and question types +- Focusing responses on particular aspects of your work +- Enabling more targeted and relevant assistance -(replace-me: Optional theory or background information relevant to this step) +For project management, a custom chat mode can help with: +- Process analysis and improvement +- Gap identification +- Best practice recommendations +- Role and responsibility clarification -### ⌨️ Activity: (replace-me: Activity title) +### ⌨️ Activity: Create and Use Project Management Deep Dive Chat Mode -1. (replace-me: First instruction) -1. (replace-me: Second instruction) -1. (replace-me: Additional instructions as needed) +1. Create a new file at `.github/chatmodes/project-management-deepdive.md` +2. Add content that defines a chat mode focused on project management process analysis +3. Use this custom chat mode to ask the following three questions: + - "Are there any gaps in the process?" + - "Suggest improvements to OctoAcme's project management process" + - "What other roles/personas should OctoAcme account for?" +4. Document the responses in the comments of this issue +5. Include insights about what the chat mode revealed about your processes + +> [!TIP] +> If you can't create the actual chat mode, simulate the deep dive by manually analyzing the documentation and answering those three questions based on your review.
Having trouble? 🤷
-- (replace-me: Troubleshooting tip or hint) -- (replace-me: Additional troubleshooting tips as needed) +- The chat mode file should include instructions for Copilot to focus on project management analysis +- Think about what specific guidance would help someone analyze project management processes +- Consider including context about OctoAcme's goals and constraints
diff --git a/.github/steps/4-step.md b/.github/steps/4-step.md new file mode 100644 index 0000000..5d868c1 --- /dev/null +++ b/.github/steps/4-step.md @@ -0,0 +1,46 @@ +## Step 4: Update the repository with new information + +Based on your analysis in the previous step, it's time to improve OctoAcme's project management processes. You'll update the repository with new information and improvements discovered through your Copilot Spaces deep dive. + +### 📖 Theory: Iterative Process Improvement + +Project management is inherently iterative. The best practices include: +- Regular review and analysis of existing processes +- Identifying gaps and improvement opportunities +- Implementing changes based on insights and feedback +- Documenting improvements for team adoption +- Measuring impact and continuing the cycle + +Effective process improvement involves: +- **Analysis**: Understanding current state and identifying gaps +- **Design**: Developing solutions and improvements +- **Implementation**: Making changes and updating documentation +- **Communication**: Ensuring team awareness and adoption + +### ⌨️ Activity: Implement Process Improvements + +Based on your analysis from Step 3, make improvements to the repository: + +1. Update existing files in the `docs/` folder to address identified gaps +2. Add new documentation files for missing processes or roles +3. Create or enhance process diagrams, templates, or checklists +4. Ensure your changes reference the insights discovered in Step 3 +5. Commit your changes with a descriptive message that mentions "process improvements" + +Your updates should include at least: +- One improvement to an existing process document +- One new file addressing a gap you identified +- Clear documentation of the changes made and why + +> [!IMPORTANT] +> Make sure your commit message includes "process improvements" so the workflow can detect your changes. + +
+Having trouble? 🤷
+ +- Focus on the most impactful improvements identified in your analysis +- Consider adding templates, checklists, or clarifying existing processes +- Common improvements include: role clarification, communication protocols, decision-making frameworks +- Even small improvements like adding examples or clarifying steps can be valuable + +
diff --git a/.github/steps/x-review.md b/.github/steps/x-review.md index e289a50..d73770b 100644 --- a/.github/steps/x-review.md +++ b/.github/steps/x-review.md @@ -1,16 +1,29 @@ ## Review -_Congratulations, you've completed this exercise and learned a lot about (replace-me: feature/product that was taught in this exercise) +_Congratulations, you've completed this exercise and learned a lot about democratizing tribal knowledge using GitHub Copilot Spaces!_ celebrate Here's a recap of your accomplishments: -- (replace-me: Accomplishment #1) -- (replace-me: Accomplishment #N) +- **Set up a knowledge hub** by adding a repository as a source to Copilot Spaces +- **Analyzed existing processes** by exploring and summarizing project management documentation +- **Created specialized tooling** with custom chat modes for deep process analysis +- **Implemented improvements** by updating documentation based on insights discovered +- **Experienced the full cycle** of knowledge democratization: capture, analyze, improve, and share + +You've successfully used GitHub Copilot Spaces to transform tribal knowledge into accessible, improvable documentation that your entire team can benefit from. This approach scales beyond project management to any domain where knowledge needs to be captured and shared effectively. ### What's next? -- (replace-me: Natural follow up Skills exercise - if there is one) -- (replace-me: Documentation link to learn more about the feature) -- (replace-me: Other resources or calls to action) +- **Explore more chat modes**: Try creating specialized modes for different aspects of your work (code review, architecture decisions, etc.) +- **Scale the approach**: Apply this pattern to other areas where your team has tribal knowledge +- **Learn more about Copilot Spaces**: [GitHub Copilot Spaces Documentation](https://docs.github.com/en/copilot) +- **Share with your team**: Introduce this workflow to help democratize knowledge across your organization + +### Key Takeaways + +- Copilot Spaces can serve as powerful knowledge management platforms +- Custom chat modes enable focused, domain-specific assistance +- Regular analysis and improvement of processes leads to better team outcomes +- Documentation becomes more valuable when it's easily accessible and continuously improved diff --git a/README.md b/README.md index 5587ae6..a5eba35 100644 --- a/README.md +++ b/README.md @@ -1,31 +1,31 @@ -# (replace-me: Exercise title) +# Democratize Tribal Knowledge Using Copilot Spaces -_(replace-me: One-line description of the exercise)_ +_Learn how to use GitHub Copilot Spaces to centralize and democratize project management knowledge within your team_ ## Welcome -- **Who is this for**: (replace-me: Target audience description) -- **What you'll learn**: (replace-me: Learning objectives) -- **What you'll build**: (replace-me: Description of what the learner will create) +- **Who is this for**: Project managers, team leads, and developers looking to streamline knowledge sharing +- **What you'll learn**: How to leverage GitHub Copilot Spaces to capture, organize, and improve project management processes +- **What you'll build**: A comprehensive knowledge management system using Copilot Spaces with custom chat modes - **Prerequisites**: - - (replace-me: Prerequisite skill/exercise) - - (replace-me: Other prerequisites) + - Basic familiarity with GitHub repositories + - Access to GitHub Copilot Spaces + - Beginner-level project management concepts -- **How long**: This exercise takes less than (replace-me: estimated time) to complete. +- **How long**: This exercise takes less than 30 minutes to complete. In this exercise, you will: -1. (replace-me: Learning objective step #1) -1. (replace-me: Learning objective step #2) -1. (replace-me: Learning objective step #N) - +1. Add a repository as a source to your Copilot Space +2. Explore and summarize project management process documentation +3. Create and use custom chat modes for deep process analysis +4. Update repository documentation based on insights discovered ### How to start this exercise Simply copy the exercise to your account, then give your favorite Octocat (Mona) **about 20 seconds** to prepare the first lesson, then **refresh the page**. - -[![](https://img.shields.io/badge/Copy%20Exercise-%E2%86%92-1f883d?style=for-the-badge&logo=github&labelColor=197935)](https://github.com/new?template_owner=skills&template_name=exercise-template&owner=%40me&name=skills-&description=Exercise:+Replace+me&visibility=public) +[![](https://img.shields.io/badge/Copy%20Exercise-%E2%86%92-1f883d?style=for-the-badge&logo=github&labelColor=197935)](https://github.com/new?template_owner=arilivigni&template_name=democratize-tribal-knowledge-using-copilot-spaces&owner=%40me&name=democratize-tribal-knowledge-using-copilot-spaces&description=Exercise:+Democratize+Tribal+Knowledge+Using+Copilot+Spaces&visibility=public)
Having trouble? 🤷
From b36b60a88a183ca5ede3f83c234d80af3ea50013 Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Mon, 22 Sep 2025 13:38:45 -0400 Subject: [PATCH 3/7] add a devcontiner config --- .devcontainer/devcontainer.json | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 .devcontainer/devcontainer.json diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json new file mode 100644 index 0000000..cde46eb --- /dev/null +++ b/.devcontainer/devcontainer.json @@ -0,0 +1,32 @@ +{ + "name": "Python 3", + "image": "mcr.microsoft.com/vscode/devcontainers/python:3.13", + "customizations": { + "vscode": { + "extensions": [ + "GitHub.copilot", + "ms-python.python", + "ms-python.debugpy", + "ms-vscode.live-server", + "mechatroner.rainbow-csv" + ], + "settings": { + "livePreview.openPreviewTarget": "External Browser", + + "chat.implicitContext.suggestedContext": false, + + // These are defaults but keeping them here for clarity and explicitness + "github.copilot.chat.codeGeneration.useInstructionFiles": true, + "chat.promptFilesLocations": { + ".github/prompts": true + }, + "chat.instructionsFilesLocations": { + ".github/instructions": true + }, + "chat.modeFilesLocations": { + ".github/chatmodes": true + } + } + } + } +} \ No newline at end of file From 8b440116e237194b22effd3ce4b296a39cb73217 Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Mon, 22 Sep 2025 13:48:39 -0400 Subject: [PATCH 4/7] rename file --- ...toacme-rols-and-personas.md => octoacme-roles-and-personas.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{octoacme-rols-and-personas.md => octoacme-roles-and-personas.md} (100%) diff --git a/docs/octoacme-rols-and-personas.md b/docs/octoacme-roles-and-personas.md similarity index 100% rename from docs/octoacme-rols-and-personas.md rename to docs/octoacme-roles-and-personas.md From 2774ed62da468078b2b1733cf119012c086bbf10 Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Mon, 22 Sep 2025 13:52:58 -0400 Subject: [PATCH 5/7] Update .devcontainer/devcontainer.json Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .devcontainer/devcontainer.json | 1 - 1 file changed, 1 deletion(-) diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json index cde46eb..8410a97 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -12,7 +12,6 @@ ], "settings": { "livePreview.openPreviewTarget": "External Browser", - "chat.implicitContext.suggestedContext": false, // These are defaults but keeping them here for clarity and explicitness From 6795c30461a20ae48d8f274266c66f0123955bf4 Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Mon, 22 Sep 2025 13:55:30 -0400 Subject: [PATCH 6/7] Update .github/steps/1-step.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .github/steps/1-step.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/steps/1-step.md b/.github/steps/1-step.md index bc2de55..cf0c177 100644 --- a/.github/steps/1-step.md +++ b/.github/steps/1-step.md @@ -29,7 +29,7 @@ Spaces help transform scattered information into an organized, searchable, and i 1. In your newly created Copilot Space, look for "Sources" or "Add Source" section 1. Add this exercise repository as a source: - - Repository URL: `https://github.com/arilivigni/democratize-tribal-knowledge-using-copilot-spaces` + - Repository URL: `` - This gives Copilot access to the project management documentation and processes 1. Wait for the repository to be indexed (this may take a few minutes) 1. Verify the repository appears in your sources list From 2b8d73607408fc05e9efc14a025f9b574809544e Mon Sep 17 00:00:00 2001 From: Ari LiVigni Date: Mon, 22 Sep 2025 13:57:06 -0400 Subject: [PATCH 7/7] Update .github/steps/1-step.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .github/steps/1-step.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/steps/1-step.md b/.github/steps/1-step.md index cf0c177..76d581e 100644 --- a/.github/steps/1-step.md +++ b/.github/steps/1-step.md @@ -29,7 +29,8 @@ Spaces help transform scattered information into an organized, searchable, and i 1. In your newly created Copilot Space, look for "Sources" or "Add Source" section 1. Add this exercise repository as a source: - - Repository URL: `` + - Repository URL: `https://github.com//` + (Replace `` with your GitHub username and `` with the name of your fork or copy of this repository. For example: `https://github.com/octocat/project-management-hub`) - This gives Copilot access to the project management documentation and processes 1. Wait for the repository to be indexed (this may take a few minutes) 1. Verify the repository appears in your sources list