Run any Skill in Manus with one click

align-feature-checklist

Stars672

Forks298

UpdatedJune 8, 2026 at 07:55

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

talkincode

talkincode/toughradius

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	align-feature-checklist
description	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.

Skill: Align Requirements / Update the Feature Checklist

Scope: all feature IDs | Baseline doc: docs/feature-checklist.md (English version feature-checklist.en.md)

When to use

Before developing any new requirement / issue.
When a requirement cannot be mapped to an existing TR-F ID.

Steps

Mapping check: find the matching TR-F0xx in docs/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-F ID
No non-goal direction was touched
CN and EN checklists are in sync

More from this repository

same repository

release-version

talkincode/toughradius

Review merged PRs since the last Git tag and decide whether a ToughRADIUS release is warranted. Use when Codex is asked to prepare a version release, audit unreleased changes, decide whether to publish, create a new release tag, or tag origin/main after PR review.

2026-07-08672

orchestrate-roadmap

talkincode/toughradius

Global orchestrator / dispatcher role. Activated when the user issues an "auto-delegate development / continue the roadmap / auto-delegate" command (without naming a specific subtask); runs the full loop - select task, pick SOP, dispatch, quality gates, open PR, self-iterate the roadmap.

2026-06-11672

review-pr

talkincode/toughradius

Independent review gate for auto-delegation PRs (TR-F022). Use after an orchestration round opens a PR, and as the first step of every new round to clear in-flight PRs - run an adversarial, CI-anchored review, request changes via labels + comments, and auto-merge only when the review passes and CI is green.

2026-06-11672

document-go-apis

talkincode/toughradius

Standard-library-style Go API documentation and comment conventions (TR-F024). Use when adding or changing exported Go identifiers, writing package comments, or backfilling godoc on a package so it reads like the Go standard library.

2026-06-09672

add-acceptance-test

talkincode/toughradius

Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.

2026-06-08672

add-adminapi-endpoint

talkincode/toughradius

Add a group of Admin REST endpoints in the management backend (TR-F012). Use when a feature needs management APIs such as create/read/update/delete.

2026-06-08672

name	align-feature-checklist
description	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.

Skill: Align Requirements / Update the Feature Checklist

Scope: all feature IDs | Baseline doc: docs/feature-checklist.md (English version feature-checklist.en.md)

When to use

Before developing any new requirement / issue.
When a requirement cannot be mapped to an existing TR-F ID.

Steps

Mapping check: find the matching TR-F0xx in docs/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-F ID
No non-goal direction was touched
CN and EN checklists are in sync