spectre-apply

Load and apply captured session knowledge to guide development work.

146|15|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/Codename-Inc/spectre --skill spectre-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectre-apply
Source: https://github.com/Codename-Inc/spectre/tree/main/plugins/spectre/skills/spectre-apply
Command: npx skills add https://github.com/Codename-Inc/spectre --skill spectre-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reuse and enforce context, decisions, and patterns from previous sessions to prevent repeated mistakes and ensure consistent implementation.

Core Features & Use Cases

  • Preserves decisions & patterns: keeps captured knowledge to avoid rediscovery and drift.
  • Instant project context: surfaces feature context, conventions, and known pitfalls for new work.
  • Use Case: when starting a feature, load this skill to surface relevant knowledge before coding, debugging, or planning.

Quick Start

Load spectre-apply before starting implementation to surface captured knowledge and guidance.

Frequently Asked Questions about spectre-apply

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply captured project knowledge to guide current development work?

To apply captured project knowledge, load this skill before starting implementation to surface relevant context, decisions, and patterns from previous sessions. This ensures consistent implementation and prevents drift by maintaining a current knowledge registry.

Why does my code drift from decisions made in previous sessions?

Code drifts from previous decisions when captured knowledge is not loaded before starting implementation. Reuse and enforce context, conventions, and known pitfalls from past sessions to prevent repeated mistakes and ensure consistent implementation.

What is the best way to preserve engineering decisions and patterns across sessions?

The best way to preserve engineering decisions is to maintain a knowledge registry that captures context and patterns. Load this registry before feature work to surface known pitfalls and avoid rediscovery during development.

When do I need to load project context before coding?

You need to load project context before coding whenever starting implementation, debugging, or feature work. Loading captured knowledge first surfaces relevant conventions and context to prevent repeated mistakes and ensure consistency.

Can I use captured knowledge to prevent repeated mistakes during debugging?

Yes, you can use captured knowledge to prevent repeated mistakes during debugging. Loading previous session context surfaces known pitfalls and engineering patterns, providing guidance to resolve issues without rediscovery.

Does applying previous session context require maintaining a knowledge registry?

Yes, applying previous session context requires maintaining a current knowledge registry to stay up to date. The skill requires loading before action to ensure the applied context, decisions, and patterns remain accurate and consistent.