proposal-maintainer

Update proposal disposition, link active tasks, and trim stale content.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/likesjx/philotic-stack --skill proposal-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proposal-maintainer
Source: https://github.com/likesjx/philotic-stack/tree/main/skills/proposal-maintainer
Command: npx skills add https://github.com/likesjx/philotic-stack --skill proposal-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining up-to-date, concise, and actionable architecture and process proposals by ensuring they are linked to active tasks and reflect current reality.

Core Features & Use Cases

  • Proposal Hygiene: Tightens proposal structure, updates disposition, and links to active tasks.
  • Status Alignment: Clarifies implemented, deferred, or superseded status.
  • Stale Content Trimming: Removes outdated or overly broad narrative.
  • Use Case: A project's core technical proposal has become outdated. This Skill can be used to update its disposition, link it to the current sprint's work items, and remove sections that are no longer relevant to the implemented architecture.

Quick Start

Use the proposal-maintainer skill to update the proposal document located at /docs/architecture/proposal.md with the latest disposition and link it to task ID #1234.

Frequently Asked Questions about proposal-maintainer

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

FAQPage Schema
How do I update architecture proposal status to match implemented reality?

To update architecture proposal status, you must revise the disposition to reflect whether the design is implemented, deferred, or superseded. This process hygiene ensures documentation accurately tracks the current development lifecycle.

What is the best way to link architecture proposals to active tasks?

Linking architecture proposals to active tasks requires mapping proposal sections to current sprint work item IDs. This task alignment clarifies which components are actively implemented and removes documentation ambiguity.

How do I remove stale content from outdated project documentation?

Removing stale content from project documentation involves trimming overly broad narrative and deleting sections that no longer reflect the implemented architecture. This keeps process proposals concise, current, and actionable.

When do I need to maintain process proposal hygiene?

You need to maintain process proposal hygiene when a core technical proposal has become outdated and no longer reflects current reality. Updating disposition and trimming stale content ensures documentation remains aligned with active tasks.

Does proposal maintenance work for general project documentation or only architecture specs?

Proposal maintenance applies to both general project documentation and architecture specification hygiene. It updates dispositions, links active tasks, and removes stale content across all development lifecycles.