Align Feature Checklist
Productivityalign-feature-checklistAlign Feature Checklist is an Agent Skill for productivity published in the talkincode/toughradius repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Align requirements with and update the feature checklist docs/feature-checklist.md. Use before developing any new requirement/issue, or when a requirement cannot be mapped to an existing TR-F ID.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/talkincode/toughradius/blob/HEAD/.agents/skills/align-feature-checklist/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/align-feature-checklist, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Align Requirements / Update the Feature Checklist
Scope: all feature IDs | Baseline doc:
docs/feature-checklist.md(English versionfeature-checklist.en.md)
When to use
- Before developing any new requirement / issue.
- When a requirement cannot be mapped to an existing
TR-FID.
Steps
- Mapping check: find the matching
TR-F0xxindocs/feature-checklist.md. If it maps, anchor it and proceed to implementation. - Non-goal check: confirm the requirement is not in
TR-N001-TR-N005(payment/orders, CRM/tickets, generic monitoring, multi-tenant SaaS, rewriting the protocol stack/framework). If it hits a non-goal, reject it or raise a scope decision first. - Cannot map: first submit a PR that only modifies the feature checklist:
- Add the feature ID, category, scope description, status, related code paths, and acceptance/dev boundary.
- Sync the English version
feature-checklist.en.md.
- Scheduling: if needed, add a milestone or subtask in
docs/roadmap.md. - Implementation: only enter code implementation after the checklist is merged; the PR references the corresponding ID.
Conventions
- The checklist describes capability boundaries only; interfaces / structs / algorithms are governed by code, tests, and inline comments.
- Deliver only one minimal closed loop at a time.
Acceptance
- The requirement is anchored to / added as a
TR-FID - No non-goal direction was touched
- CN and EN checklists are in sync