skills.rest
CuongTran69
CuongTran69COMMUNITY
Explore all skills by this author →
GitHub

chore

Plans software maintenance and technical system work during discovery and scoping.

Updated Aug 27, 2026
Search Tags:#architecture#scoping#specification#discovery#maintenance#test-strategy#impact-assessment
One-click install
npx skills add https://github.com/CuongTran69/tramthientra --skill chore-cuongtran69
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chore
Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/chore
Command: npx skills add https://github.com/CuongTran69/tramthientra --skill chore-cuongtran69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and maintainers systematically plan maintenance work by exploring scope, assessing impact, mapping architecture, and choosing an implementation path that minimizes risk and rework.

Core Features & Use Cases

  • Discovery-first workflow: Requires invoking an "explore" mode to load a consistent stance, verification steps, workflow conventions, and subagent protocols before proceeding.
  • Scope and impact assessment: Guides a Feynman-style restatement, clarifying questions, assumption challenges, and architecture mapping to surface hidden complexity.
  • Compare and recommend options: Brainstorms approaches, sketches tradeoffs, builds comparison tables, and recommends an implementation path with testing and verification guidance.
  • Use Case: Triage a legacy refactor by mapping affected modules, estimating testing gaps, choosing minimal vs. comprehensive strategies, and producing a verifier-ready checklist or spec.

Quick Start

Invoke the chore skill's explore mode, then ask it to map affected components, assess impact, and recommend an implementation plan.

Frequently Asked Questions about chore

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

FAQPage Schema
How do I plan software maintenance work for legacy repositories?▼

Use a discovery-first workflow to map affected architecture, assess impact, and surface hidden complexity before implementation. This approach clarifies scope, identifies testing gaps, and produces a verifier-ready checklist to minimize maintenance risk.

How do I assess the impact and testing needs of a legacy refactor?▼

Assess impact and test needs by mapping affected components and challenging assumptions. This workflow estimates testing gaps and builds a targeted test strategy to verify the refactor without requiring a full system rewrite.

What is the best way to compare implementation options for system maintenance?▼

Compare implementation options by building tradeoff tables that evaluate minimal versus comprehensive strategies. This approach sketches specific approaches, evaluates risks, and recommends a maintenance path with tailored testing and verification guidance.

Can I generate a specification document after scoping a maintenance task?▼

Yes, you can generate an optional specification document after scoping a maintenance task. This spec creation follows risk assessment and test strategy definition, providing a verifier-ready checklist for the implementation phase.

Does this maintenance planning workflow require a specific starting mode?▼

Yes, this maintenance planning workflow requires an initial explore invocation. This discovery mode loads verification steps, workflow conventions, and subagent protocols to ensure consistent scoping before proceeding with implementation.

Related Skills

Explore More Software Engineering Skills→
nullmastermindnullmastermind
9

chore

Plan maintenance work by exploring scope and assessing impact.

Community
Intermediate
NikiforovAllNikiforovAll
137

spec-driven

Coordinate subagents through spec-driven development phases with approval gates.

Community
Advanced
nullmastermindnullmastermind
9

refactor

Plan code refactoring with architecture mapping, dependency tracing, and risk assessment.

Community
Advanced
zhangzhang-111-izhangzhang-111-i
2

tech-debt-tracker

Scan codebases to identify, prioritize, and track technical debt.

Community
Advanced