Skip to content

phuryn/product-engineering / app-stack/skills/app-lifecycle

app-lifecycle

Verified

Planning a SaaS stage, 'what's next', 'where are we', calling a stage done: the detailed path from an idea to production, each stage with its done-when.

FileKindSize
SKILL.mdskill md24.4 KB
receipts.mdmarkdown5.3 KB
references/brief.mdmarkdown3.3 KB
references/capabilities.mdmarkdown16.7 KB
references/decisions.mdmarkdown4.0 KB
references/default-choices.mdmarkdown22.7 KB
references/plan.mdmarkdown7.2 KB
references/product-section.mdmarkdown4.4 KB
references/product-shapes.mdmarkdown5.2 KB
references/stage-brief.mdmarkdown8.0 KB
references/stages.mdmarkdown42.3 KB
references/strategy.mdmarkdown1.2 KB

references/strategy.md

View on GitHub
# The product strategy (optional)

**What it is for:** where the product is going, as the owner has confirmed it, with the date of that confirmation.

**Read it** when a decision turns on direction rather than on what the product does today.

**Rules**

- **Optional. Leave it a stub until the owner confirms a strategy.**
- **Never fill it with a draft the owner has not confirmed.** The brief describes the product as it is meant to work now; a guess written here would be read by every later session as a commitment.
- **Read it only once the owner has confirmed one** — an unconfirmed strategy is not an input to a decision.

## Skeleton — copy from here

```markdown
# Product strategy (optional)

Where the product is going, as the owner has confirmed it, with the date of that confirmation. Read it when a decision turns on direction rather than on what the product does today. Leave this file a stub until the owner confirms a strategy, and never fill it with a draft the owner has not confirmed — the brief describes the product as it is meant to work now, and a guess written here would be read as a commitment.

<Confirmed by the owner on YYYY-MM-DD:>
<…>
```
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall