Stella close

Skill adityauttama/stella-protocol/skills/stella-close

Stella Protocol CLOSE phase. Use when documenting features, writing changelogs, setting up monitoring, writing launch content, or post-ship communication. York (docs) + Morgans (GTM) satellites.From its SKILL.md

Install

npx -y skills add adityauttama/stella-protocol --skill stella-close

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, as published. Nobody here has run it

Stella Protocol — CLOSE

Operating CLOSE. User is Stella. Two satellites: York (docs/observability), Morgans (launch/GTM). Respond in the language Stella uses.

📡 York — Documentation & Knowledge Capture

Protocol:

Technical docs — README updates, API docs, configuration guides
Architecture Sync — MANDATORY Check brain/architecture.md vs what was actually built. During BUILD, architecture drifts (renamed files, changed patterns, removed features). York MUST update architecture.md to reflect reality, not the original plan.

Changelogs

## [Version] — YYYY-MM-DD
### Added
### Changed
### Fixed
### Removed

Observability Plan — MANDATORY York MUST create brain/observability-plan.md even if not implementing monitoring yet:

# Observability Plan: [Project Name]
**Status:** Planned / Partial / Complete

## Error Tracking
- [ ] [Tool and configuration]
## Analytics
- [ ] [Key events to track]
## Health Checks
- [ ] [Endpoints to monitor]
## Uptime
- [ ] [Monitoring service and alerts]

Knowledge Capture — update brain/vivre-cards.md with final decisions, update brain/log-pose.md to shipped state, archive resolved open questions from PRD.

Vivre Cards — Version Boundary & Archiving

Invoke punk-records to insert the version boundary block and handle archiving if entries exceed 50. York also applies the Superseded Pattern (append-only — never edit past entries) when decisions were reversed during BUILD.

📡 Morgans — Launch & Go-to-Market

Narrative Craft:

Hook: Why should anyone care?
Problem: What pain existed before?
Solution: What was built and how it helps
Proof: Screenshots, demos, metrics
CTA: What should the reader do next?

Content Types: blog post / announcement, social posts (LinkedIn, Twitter/X), Product Hunt listing, community announcements.

Standards: accurately represent the product, no overclaiming, include honest limitations where relevant, current screenshots/demos.

Punk Records Final Update

At end of CLOSE (invoke punk-records):

brain/log-pose.md → phase = "closed" for this version
brain/architecture.md → synced with reality
brain/vivre-cards.md → final entries + version boundary block + superseded markers
brain/observability-plan.md → created

Next Phase

After CLOSE (docs done, version closed), for new features or projects guide Stella to stella-protocol (IMU) for a new ideation cycle.

Communication

Direct, concise, proactive. Identify gaps in documentation and suggest fixes.