spec-update

Save user-declared project conventions to .superharness/spec files.

4|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Mrlyk/superharness --skill spec-update-mrlyk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-update
Source: https://github.com/Mrlyk/superharness/tree/main/skills/spec-update
Command: npx skills add https://github.com/Mrlyk/superharness --skill spec-update-mrlyk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and persist user-declared project conventions so decisions are documented, consistent across the team, and automatically loaded into future AI sessions. This prevents ad-hoc rules from being lost or inconsistently applied and reduces ambiguity for new contributors.

Core Features & Use Cases

  • Capture explicit conventions: Parse a single user instruction, convert it into a descriptive spec entry, and ensure the entry uses a factual tone.
  • Route and detect conflicts: Determine the appropriate .superharness/spec target file, read existing content, surface conflicts with clear choices (replace, mark migration, append, cancel), and avoid silent overwrites.
  • Human-in-the-loop write and trace: Present the exact markdown to write, require explicit user confirmation, commit with a standardized message, and append trace logs to the active task when applicable.
  • Use Case: A developer states "From now on use zustand for state management" and the skill rewrites that into a descriptive spec entry and records it in the proper spec file after confirmation.

Quick Start

Save the user's convention "Use zustand for state management" into the appropriate .superharness/spec file and confirm the write when prompted.

Frequently Asked Questions about spec-update

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

FAQPage Schema
How do I save project conventions and rules to my repository?

To save project conventions, this skill parses your instruction into a descriptive spec entry and routes it to the appropriate .superharness/spec file. It requires explicit user confirmation before committing the update with a standardized message to ensure rules are documented.

What happens when a new project rule conflicts with existing repo conventions?

When a new project rule conflicts with existing repo conventions, the skill reads the target spec file and surfaces the conflict with clear choices. You can choose to replace the entry, mark it for migration, append it, or cancel the update to prevent silent overwrites.

How do I persist ad-hoc coding guidelines decided during a brainstorming session?

To persist ad-hoc coding guidelines decided during a brainstorming session, simply state the rule explicitly. The skill converts your statement into a factual spec entry, presents the exact markdown for review, and records it in the proper spec file after your confirmation.

Can I automatically load team project rules into future AI sessions?

Yes, you can automatically load team project rules into future AI sessions by saving them to the .superharness/spec directory. This prevents ad-hoc rules from being lost and reduces ambiguity for new contributors by keeping decisions documented and consistent.

Does saving a project spec require manual git commits?

Saving a project spec does not require manual git commits because the skill handles the write process autonomously. After you confirm the markdown entry, it commits the update with a standardized message and appends trace logs to the active task when applicable.