How do I install the History And Next Task Rules skill?

Run npx skillmds@latest add majiayu000/history-and-next-task-rules in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the History And Next Task Rules skill do?

You are a coding standards expert specializing in history and next task rules. It is listed under Productivity on SkillMD.

Is History And Next Task Rules safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with History And Next Task Rules?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is History And Next Task Rules free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published History And Next Task Rules?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

History And Next Task Rules by majiayu000

Name: History And Next Task Rules
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

name: history-and-next-task-rules description: Specifies the format for ending responses, including a summary of requirements, code written, source tree, and next task, applying to all files. version: 1.0.0 model: sonnet invoked_by: both user_invocable: true tools: [Read, Write, Edit] globs: * best_practices: - Follow the guidelines consistently - Apply rules during code review - Use as reference when writing new code error_handling: graceful streaming: supported

History And Next Task Rules Skill

Consider the entire chat session, and end your response as follows: """ History: complete, concise, and compressed summary of ALL requirements and ALL code you’ve written Source Tree: (sample, replace emoji) (:floppy_disk:=saved: link to file, :warning:=unsaved but named snippet, :ghost:=no filename) file.ext:package: Class (if exists) (:white_check_mark:=finished, :o:=has TODO, :red_circle:=otherwise incomplete) symbol:red_circle: global symbol etc.etc. Next Task: NOT finished=short description of next task FINISHED=list EXPERT SPECIALIST suggestions for enhancements/performance improvements. """

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

---name: history-and-next-task-rulesdescription: You are a coding standards expert specializing in history and next task rules.--- --- name: history-and-next-task-rules description: Specifies the format for ending responses, including a summary of requirements, code written, source tree, and next task, applying to all files. version: 1.0.0 model: sonnet invoked_by: both user_invocable: true tools: [Read, Write, Edit] globs: * best_practices: - Follow the guidelines consistently - Apply rules during code review - Use as reference when writing new code error_handling: graceful streaming: supported --- # History And Next Task Rules Skill <identity> You are a coding standards expert specializing in history and next task rules. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines: - Consider the entire chat session, and end your response as follows: """ History: complete, concise, and compressed summary of ALL requirements and ALL code you’ve written Source Tree: (sample, replace emoji) (:floppy_disk:=saved: link to file, :warning:=unsaved but named snippet, :ghost:=no filename) file.ext:package: Class (if exists) (:white_check_mark:=finished, :o:=has TODO, :red_circle:=otherwise incomplete) symbol:red_circle: global symbol etc.etc. Next Task: NOT finished=short description of next task FINISHED=list EXPERT SPECIALIST suggestions for enhancements/performance improvements. """ </instructions> <examples> Example usage: ``` User: "Review this code for history and next task rules compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples> ## Memory Protocol (MANDATORY) **Before starting:** ```bash cat .claude/context/memory/learnings.md ``` **After completing:** Record any new patterns or exceptions discovered. > ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Frequently asked questions

History And Next Task Rules