vp crystallize

Other Community v0.8.0

Skill notes

Invocation Banner

Output this banner as the first thing on every invocation — before questions, work, or any other output: </greeting> <version_check>

Version Update Check (ENH-072)

After displaying the greeting banner, run: If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output: Replace {latest_version} with stdout from the command, {current} with the installed version, {adapter_id} with the active adapter (claude-code / cursor / antigravity / codex / copilot).

Persona Context Injection (ENH-073)

At skill start, run: Inject the output as ## User Persona context before any task execution. Silent if command unavailable or errors. </persona_context> <adapter id="claude-code">

B. User Prompting

Prompt user conversationally with numbered list options.

C. Tool Usage

Use Claude Code tools: Bash (shell), Read (file), Edit + Write (file write/patch), Grep (search), Glob (file patterns), LS, WebSearch, WebFetch, Agent (spawn subagent — multi-level nesting supported) Interactive: AskUserQuestion (deferred — preload via ToolSearch before first call) </adapter>

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@0-CODE · v0.8.0 · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Node.js · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Collect Project Metadata

FEAT-009: Load `.viepilot/META.md` + global profile file first (`workflows/crystallize.md`); set `profile_resolved` or `none`; pre-fill org/website when profile is present. Ask user for (confirm proposals from profile if present): Project name, description Organization name, website Package Base ID (e.g., com.company.project)

02
Step 1: Analyze Brainstorm

Load all brainstorm sessions Extract: decisions, architecture, schemas, features Extract selected tech stacks Phase assignment (ENH-030): parse `## Phases` from brainstorm sessions; build `phases_inventory`; run phase assignment gate (all features must have a phase — full contract: `workflows/crystallize.md` Step 1) Validate completeness (tech stack, features, schema/API clarity, phase assignment gate)

03
Step 1A: Consume UI direction (if present)

Read `.viepilot/ui-direction/{session-id}/notes.md` first, then `style.css`, then HTML: Multi-page: if `pages/*.html` exists → require `## Pages inventory` in `notes.md`, validate it lists every page file, read each `pages/*.html` plus hub `index.html` for navigation. Legacy: no `pages/` → read `index.html` + `style.css` as before. Carry approved layout/component decisions into architecture + roadmap artifacts; architecture must reference all pages from inventory when multi-page.

04
Step 1B: Official stack research (mandatory)

For every selected stack, research official docs and authoritative sources Build concise "Do / Don't / Pitfalls" guidance If guidance is uncertain, ask user before locking decisions Tool policy: Use `WebSearch` to discover candidate sources

05
Step 1C: Write stack cache

Persist guidance to `~/.viepilot/stacks/{stack}/...` Create `.viepilot/STACKS.md` for lookup mapping

06
Step 2: Generate AI-GUIDE.md

Quick lookup table Context loading strategy File relationships FEAT-009: Quick context for `profile_id` + profile path when resolved

07
Step 3: Generate PROJECT-META.md

Project info Organization info Package structure Developer info File headers template

08
Step 4: Generate ARCHITECTURE.md

System overview FEAT-009: Section `## ViePilot organization context` when profile is present (or none line) Services definitions Data flow Technology decisions

09
Step 5: Generate PROJECT-CONTEXT.md

FEAT-009: Block `## ViePilot active profile (FEAT-009)` when binding is present Domain knowledge Business rules Conventions Constraints

10
Step 6: Generate SYSTEM-RULES.md

Architecture rules Coding rules Comment standards (good/bad examples) Versioning (SemVer) Git conventions (Conventional Commits)

11
Step 7: Generate ROADMAP.md

Use `templates/project/ROADMAP.md` — phases in order (Phase 1, Phase 2...) from `phases_inventory`; no Post-MVP block Each phase: tasks, acceptance criteria, verification commands Self-check before finalize: all phases from phases_inventory appear in ROADMAP; if mismatch → stop and ask user — see `workflows/crystallize.md` Step 7

12
Step 8: Generate schemas/

database-schema.sql kafka-topics.yaml api-contracts.yaml

13
Step 9: Initialize TRACKER.md

Current state Progress overview Decision log Version info

14
Step 10: Generate Project Files

CHANGELOG.md CONTRIBUTING.md CONTRIBUTORS.md LICENSE README.md (updated)

15
Step 11: Commit & Confirm

Git commit all artifacts Display summary Suggest: `/vp-auto` </process> <success_criteria>

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.