wingmate.

Community toolkit for Copilot Cowork

Big ideas deserve
a good wingmate.

AI can help you build an app.
Wingmate helps you ask the right questions.

Five skills. One conversation. A thoughtful route from “what if” to an app you’re ready to stand behind.

Download the skill pack Find your flight path

ZIP bundle · Extract first, then import the five inner skill ZIPs.

Less overwhelm

One useful question at a time.

A recommendation and lettered alternatives, not a wall of questions. Follow the important unknowns before moving on.

More continuity

Your thinking travels with you.

Decisions, evidence, and approvals stay in a shared workbook. No need to explain your idea again at every stage.

Clearer boundaries

A co-pilot, not a permission slip.

Explicit, scoped approvals matter. The skills guide the work; they don’t override platform controls or publish your app.

Five skills. Six stages.

A good route leaves
room for a course correction.

Start with an idea. Build with Cowork’s native /app. Return to the skills to challenge, test, and review. Expand any stage for the details.

01Find your direction

Shape My App

Turn a one-sentence idea into a clear outcome, a sensible scope, and a shared picture of success.

What happens in Shape

Work through users, workflows, exceptions, and acceptance criteria one question at a time, with a recommended answer.

Bring a brand guide or a screenshot if you have one. Visual discovery is optional: “recommend something for me” is a perfectly good starting point.

Leave with: a grounded brief and the first entries in your App Workbook.

Download Shape My App
02Know your foundations

Design My Data

Understand the records, sources, ownership, and access your app needs before committing to a design.

What happens in Data

Review what already exists, what can be reused, and which operations are actually needed. Separate reading data from permission to change it.

Leave with: reviewed data decisions and access boundaries, not automatically provisioned resources or connected business data.

Download Design My Data
03You take the controls

Build with /app

Use Cowork’s native app-building capability to turn the reviewed brief into an explicitly scoped preview.

What happens in Build

You invoke /app in the same conversation. It is a native Cowork command, not a sixth Wingmate skill.

Review the proposed actions and native approvals. App generation can create persistent resources; requesting synthetic data does not guarantee a resource-free build.

Return to a pack skill afterward. Native /app results reconcile into the workbook and journey on that next skill turn—not through background synchronization.

Included in Cowork where available.
No additional Wingmate download.

04Try the awkward cases

Pressure-Test My Prototype

Challenge the workflow and visual direction. Find the gaps while changing course is still inexpensive.

What happens in Pressure-test

Review real scenarios, confusing interactions, and failure paths. Use targeted human UI evidence, such as a redacted screenshot or a specific observed result.

Run safe functional checks only when actual non-browser code or authorized service tools are available. Record gaps and agree on scoped repairs.

Leave with: prioritized findings, evidence, and a clear next iteration.

Download Pressure-Test My Prototype
05Trade guesses for evidence

Prove My App Works

Check the acceptance criteria against what actually happened. Keep unknowns visible, not quietly checked off.

What happens in Prove

Execute safe functional tests through available non-browser app-code or authorized service tools. Test mutations need explicit approval for an isolated, synthetic-data scope.

For UI checks, ask for targeted human evidence. If execution is unavailable, record the check as unverified or blocked. Generated test plans and source review are not test passes.

Leave with: actual results, remaining risks, and honest limits.

Download Prove My App Works
06Land responsibly

Release My App Responsibly

Review the exact build, intended audience, support, and recovery before a human decides to publish.

What happens in Release

Review exposed data and representative-recipient access, unresolved findings, and the plan if something goes wrong. Approval applies to a specific scope and build, not every future change.

Leave with: a release decision and recorded conditions. The skill does not publish, share the app, change permissions, or treat silence as approval.

Download Release My App Responsibly

Select Wingmate skills by name through Sources as needed. Their names are not slash commands; only native /app is.

A shared memory. A visible next step.

Keep the thread.
See the journey.

Two companion files keep the work connected. The active skill updates the journey after every workbook update—including individual answers and test results.

Stay in the same conversation. These are persistent snapshots, not a live service: native /app work is reconciled on the next pack-skill turn. There is no background sync; a failed save must be reported as unsaved or stale.

The record · Markdown

App-Workbook.md

Your requirements, vocabulary, visual direction, data decisions, findings, evidence, revisions, and explicit approvals.

Download the blank workbook
The map · Local HTML

App-Journey.html

A personalized, interactive six-stage map with your current position, blockers, and next prompt to bring back to the conversation.

Preview the blank journey template

Standalone templates are optional. Do not upload the HTML as a skill. The skills create and personalize it. The blank preview is not your project’s live progress.

Small start. Clear next step.

Your idea is enough.

No requirements document to write first. No secrets required. Bring a simple problem you would like to solve.

  1. Download & extract

    Get the skill pack and extract the outer Wingmate-Skills.zip. Inside are five individual skill ZIPs plus companion templates. The outer bundle is not the skill upload.

  2. Add the five skills

    In Cowork, go to Customize → Skills and upload each inner ZIP separately. When updating, preserve your current workbook and journey; replace old skill versions rather than leaving duplicates.

  3. Start shaping

    Activate Shape My App through Sources and share a one-sentence idea. Stay in that same chat for the journey, selecting the next skill when needed.

Try a first sentence like this

“I want an app that helps our team spot manufacturing line problems and manage cases to resolve them.”

Wingmate helps you work out the next question.

Download the skill pack View pack metadata & checksums

An honest preflight check

Useful guidance.
Not a guarantee.

Wingmate is an independent community pilot. Locally validated packaging and interaction behavior are not tenant certification or proof that a model will follow every instruction.

Built for the current Cowork pilot

Current artifact packaging and pilot work target Microsoft Copilot Cowork. File, HTML, clipboard, and tool support vary by environment. Copilot Studio is an intended future validation target—not a supported compatibility or verified import claim.

Evidence without browser automation

Functional tests use only actually available, safe non-browser code or authorized service tools. UI checks rely on targeted human evidence.

No browser or computer-use probes, retries, setup changes, or alternate automation runners. No claim of a test pass without execution. If a check cannot run, that limit stays visible.

You own approvals and publication

The skills provide instruction guidance, not policy enforcement. Real permissions, organizational policy, and native approval controls still apply. Approvals must be explicit and scoped; the skills do not publish apps.

Local files, no added telemetry

This page and the local journey template have no tracking, external assets, or live remote API connections. Wingmate requires no secrets. A website host may still keep ordinary access logs, and work inside Cowork remains subject to Microsoft’s service terms and your organization’s policies.

Use synthetic data for the pilot. Keep credentials and sensitive business information out of shared workbooks, prompts, and screenshots.