feature-status-registry
Skill4 starsChanged 3 months agoApache-2.0View on GitHub
Pattern for tracking feature implementation status in derived projects. Reference when a derived project needs to track which framework features are implemented, planned, or deferred.
In this repository25 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adr-writingSkill
- authoring-goal-contractsSkill
- collaborating-asyncSkill
- committing-changesSkill
- cross-agent-dispatchSkill
- documenting-decisionsSkill
- grill-meSkill
- grill-yourselfSkill
- handling-micro-fixesSkill
- multi-instance-dispatchSkill
- notifying-the-developerSkill
- orchestrating-goal-loopsSkill
- orchestrating-lean-dispatchSkill
- performance-playbookSkill
- python-project-patternsSkill
- recovering-from-failuresSkill
- running-build-checkpointsSkill
- searching-prior-artSkill
- security-checklistSkill
- selecting-review-gatesSkill
- severity-calibrationSkill
- syncing-framework-docsSkill
- testing-playbookSkill
- wrapping-up-sessionsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this pattern in derived projects (not the template itself) to track which framework features have been implemented, adapted, or …
- Very specific: line 18
Create a FEATURE_STATUS.md file at the project root with this structure:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Feature Status Registry Pattern
When to Use
Use this pattern in derived projects (not the template itself) to track which framework features have been implemented, adapted, or deferred. This is especially useful when:
- A derived project adopts the framework incrementally
- Multiple developers need visibility into what's been built vs. what's planned
- The project needs to track divergence from the template's capabilities
Pattern: FEATURE_STATUS.md
Create a FEATURE_STATUS.md file at the project root with this structure:
# Feature Status
> Tracks implementation status of framework capabilities in this project.
> Last updated: YYYY-MM-DD
## Status Legend
| Status | Meaning |
|--------|---------|
| DONE | Fully implemented and tested |
| IN PROGRESS | Currently being built |
| PLANNED | Scheduled for a future sprint |
| ADAPTED | Implemented with project-specific modifications |
| DEFERRED | Intentionally postponed (with rationale) |
| N/A | Not applicable to this project |
## Core Framework
| Feature | Status | Notes |
|---------|--------|-------|
| Quality gate | DONE | |
| Capture pipeline | DONE | |
| Multi-agent review | DONE | |
| Education gates | PLANNED | Sprint 3 |
| Lineage tracking | ADAPTED | Simplified for single-repo |
## Project-Specific Features
| Feature | Status | Notes |
|---------|--------|-------|
| [feature name] | [status] | [notes] |Guidelines
- Update at sprint boundaries — not after every commit
- Include rationale for DEFERRED — prevents the same question from being asked repeatedly
- Track ADAPTED features separately — these are intentional divergences from the template
- Link to ADRs where adaptation decisions are documented
- Keep it flat — resist the urge to nest categories deeply; a single table per section is sufficient
Relationship to Other Tracking
FEATURE_STATUS.mdtracks what is implemented (high-level capability view)BUILD_STATUS.mdtracks current session work (ephemeral, session-scoped)framework-lineage.yamltracks structural drift from the template (file-level)memory/lessons/adoption-log.mdtracks patterns evaluated from external projects
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

