retrospect

AI Community

Skill notes

Purpose

This skill helps maintain and improve the quality of AI-assisted development by: Identifying patterns where user corrections reveal gaps in instructions Detecting violations of existing coding standards and conventions Updating instructions to prevent repeating the same mistakes Creating a feedback loop for continuous improvement

When to Use This Skill

Use this skill when: A user points out a recurring mistake or anti-pattern Multiple corrections have been made during a session You want to ensure coding standards are being followed A user explicitly requests instruction review or updates

Phase 1: Session Analysis

Objective: Review the current chat session to identify learning opportunities. 1.1 Collect User Corrections Scan the conversation history for: Direct corrections: "No, you should..." or "That's wrong, the correct way is..." Repeated mistakes: Same issue corrected multiple times

Phase 2: Constitution Review

Objective: Verify compliance with existing standards and constitutions. 2.1 Load Current Constitutions Read all relevant constitution and standards documents: AGENTS.md - Agent architecture, behavior patterns, and operational guidelines SDD files (Software Design Documents) - System design principles and requirements

Phase 3: Constitution Update

Objective: Formalize lessons learned into actionable constitutions. Update Strategy: Identify the appropriate constitution document to update Check if a skill exists for updating that document type If a skill exists, invoke it with the update requirements

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

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

01
Phase 1: Session Analysis

Objective: Review the current chat session to identify learning opportunities. 1.1 Collect User Corrections Scan the conversation history for: Direct corrections: "No, you should..." or "That's wrong, the correct way is..." Repeated mistakes: Same issue corrected multiple times

02
Phase 2: Constitution Review

Objective: Verify compliance with existing standards and constitutions. 2.1 Load Current Constitutions Read all relevant constitution and standards documents: `AGENTS.md` - Agent architecture, behavior patterns, and operational guidelines `SDD` files (Software Design Documents) - System design principles and requirements

03
Phase 3: Constitution Update

Objective: Formalize lessons learned into actionable constitutions. Update Strategy: Identify the appropriate constitution document to update Check if a skill exists for updating that document type If a skill exists, invoke it with the update requirements

04
Phase 4: Validation

Objective: Ensure updates are effective and non-disruptive. 4.1 Review Changes Ensure new instructions don't contradict existing ones Verify examples are accurate and compilable Check that rationale is clear and convincing

Discussion

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