App Journey - not yet personalized
Shape the idea. Review the data. Build. Challenge the prototype. Prove it works. Release responsibly.
Stay in this same Cowork conversation. This guide explains the route; the App Workbook holds the decisions and evidence.
Where we are now
- Current stage
- Not yet established
- What we are working on
- Your first skill will personalize this guide from the conversation.
- Next action
- Describe your idea using Shape My App, or ask the relevant skill to resume existing work.
- What is blocking progress
- Not assessed. No gates or results are assumed.
- Recent progress
- No recorded progress in this template.
Copy, then paste into Cowork yourself. Buttons do not invoke skills or approve actions. If copying is unavailable, select the prompt manually.
The whole journey
1. Shape the idea Not started
Skill: Shape My App. Clarify who needs the app, what outcome matters, workflow exceptions, scope, and visual direction. Grilling means one useful question at a time, with a recommendation.
Produces: a brief, shared business terms, visual direction, and measurable acceptance criteria. Gate: explicit approval of the current brief.
No brief approval recorded.
2. Review the data Not started
Skill: Design My Data. Reuse authoritative sources, clarify records and relationships, and determine who may see or change what.
Produces: a data/access plan and scoped build handoff. Gate: current brief and data-plan approvals; unresolved live-data capabilities stay blocked.
Source ownership, operations, and exposure are not yet reviewed.
3. Build the approved plan Not started
Native skill: /app. The human invokes the native builder here, after reviewing its proposed actions. This pack does not invoke it automatically.
Produces: an identifiable preview for review, not release proof. Gate: valid brief/data approvals and an explicitly scoped handoff. Do not publish.
Awaiting approved build scope. This card will contain the scoped /app prompt when ready.
4. Pressure-test the prototype Not started
Skill: Pressure-Test My Prototype. Challenge realistic workflows and exceptions, compare the design with your direction, and find functional gaps.
Produces: findings tied to requirements, safe non-browser test results where available, and scoped repairs. Gate: critical findings resolved and prototype approval.
No preview review evidence recorded. Screenshots alone do not prove interactive behavior.
5. Prove it works Not started
Skill: Prove My App Works. Connect each requirement to actual test evidence for the current build. Recheck failed and affected paths after repairs.
Produces: passed, failed, blocked, not-run, and stale results with evidence limits. Gate: required checks have current passing evidence; a checklist is not a pass.
No acceptance execution recorded. Static findings and human reports remain clearly attributed.
6. Release responsibly Not started
Skill: Release My App Responsibly. Review the exact build, audience, data exposure, ownership, support, and recovery before sharing.
Produces: a human-gated release handoff. Gate: current evidence and explicit release approval. Publication is a separate human action and requires evidence afterward.
Release has not been approved; publication is unverified.
About this saved snapshot
- Workbook location
- Not saved - template only
- Source workbook revision
- Not established
- Source workbook last updated
- Not established
- Journey refreshed
- Not established
- Build being reviewed
- No build identified
The skills refresh this file alongside workbook updates while active. It is not a live connection. After native /app work, the next pack skill reconciles the result. If the workbook is newer, ask the current skill to refresh this guide.