hahaxiang27

hahaxiang27/FlowHarness

Command

A Sprint-end review command that checks project code against the team’s written rules and produces an acceptance result. A Sprint is a fixed period of development work.

hahaxiang27/FlowHarness

Command

为当前用户故事或 Sprint 编写并运è¡?[E2ETOOL] E2E 测试ã€?triggers.

hahaxiang27/FlowHarness

Command

A four-level verification command for completed software tasks. It checks whether the code builds, matches its documented contracts, works end to end, and follows the project's governing rules.

hahaxiang27/FlowHarness

Command

A task-execution command that completes the next or a selected development task and runs two levels of checks. TDD means writing or using tests as part of development.

hahaxiang27/FlowHarness

Command

A repair command that addresses items a verification step marked as failed, then runs the relevant checks again.

hahaxiang27/FlowHarness

Command

A reporting command that calculates five groups of Sprint measures from progress files and creates a health report. A Sprint is a fixed period of development work.

hahaxiang27/FlowHarness

Command

A planning command that turns a task list into smaller Sprint plans and progress files. A Sprint is a fixed period of development work.

hahaxiang27/FlowHarness

Command

关联 peer-reviewer sub-agent 独立è·?peer review，产å‡?review 报告，不è¿?evaluator 流程ã€?triggers.

hahaxiang27/FlowHarness

Command

A workflow that creates a boundary statement for a development sprint, listing what is included, excluded, and constrained by dependencies. A sprint is a planned period of focused development work.

hahaxiang27/FlowHarness

Command

A manual checker for whether a feature specification is split into manageable user stories and tasks. It reads the feature’s specification, task list, and project rules, then reports the counts.

hahaxiang27/FlowHarness

Command

A command for starting or resuming a Harness Sprint, a planned group of development tasks. It reads the sprint's progress and project rules, then reports what should happen next.

hahaxiang27/FlowHarness

Command

A command for recording a proposed project rule or a lesson from an incident in a pending document. The entry waits for a later human review before becoming part of the project constitution, which is the document defining the project’s rules.

hahaxiang27/FlowHarness

Command

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

hahaxiang27/FlowHarness

Command

Generate a custom checklist for the current feature based on user requirements.

hahaxiang27/FlowHarness

Command

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

hahaxiang27/FlowHarness

Command

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

hahaxiang27/FlowHarness

Command

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

hahaxiang27/FlowHarness

Command

Execute the implementation planning workflow using the plan template to generate design artifacts.

hahaxiang27/FlowHarness

Command

Create or update the feature specification from a natural language feature description.

hahaxiang27/FlowHarness

Command

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

hahaxiang27/FlowHarness

Command

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

hahaxiang27/FlowHarness

Cursor rule

A set of rules for coordinating SpecKit and Harness, a workflow system with a visible progress dashboard. It requires each concrete command to be completed and recorded before moving to the next one.